Fortrip

Name: Fortrip
Author: FortripEngineering

by FortripEngineeringversion 1.4.13i★ –iComputer or cloud

Registry nameio.github.FortripEngineering/fortrip

Install

Overview

Description from the maker (original English)

Search hotels worldwide, compare live room rates, book and pay securely, and cancel bookings.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.fortrip.ai/

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "fortrip": {
      "command": "npx",
      "args": [
        "-y",
        "fortrip",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add --transport http fortrip https://mcp.fortrip.ai/

Or run it on your computer

claude mcp add fortrip -- npx -y fortrip mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "fortrip": {
      "url": "https://mcp.fortrip.ai/"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "fortrip": {
      "command": "npx",
      "args": [
        "-y",
        "fortrip",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "fortrip": {
      "type": "http",
      "url": "https://mcp.fortrip.ai/"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "fortrip": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "fortrip",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.fortrip.ai/

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account FortripEngineering, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 380 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7234 servers in this category
Published to the registry more recently than 99% of the other 7234 servers in this category
Basic checks equal to or better than 100% of the other 7234 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Fortrip safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.4.13) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Fortrip

Fortrip's public agent surface in one repository: the fortrip command-line tool for hotel search, live offers and orders, the contract that every agent surface shares, and the store listings that point agents at Fortrip. Hotels only for now.

Everything here talks to Fortrip API v1, https://api.fortrip.ai/v1, or to the hosted MCP server, https://mcp.fortrip.ai/, as a Fortrip user who has signed in with OAuth in the browser.

Using Fortrip

From a shell, or an agent with one: npx -y fortrip . People start with npx -y fortrip login. Agents run npx -y fortrip guide and sign in through the loginUrl a command prints when it exits 3. The CLI's README has the commands, sign-in and exit codes.
In an MCP client: connect the hosted server https://mcp.fortrip.ai/ if the client supports remote servers with OAuth, or run the local bridge, npx -y fortrip mcp. The CLI's README has the config for Claude Desktop, Cursor, Codex and Claude Code. The Claude and OpenAI plugins use the hosted server.
In Claude Code, as a plugin (the hosted server plus Fortrip's skill):

  /plugin marketplace add FortripEngineering/fortrip

/plugin install fortrip@fortrip

As a skill, for agents that can run shell commands but don't have Fortrip's MCP tools:

  npx skills add FortripEngineering/fortrip --skill fortrip-cli

Layout

Path	What it is	How it's published
`packages/contract`	The contract of Fortrip API v1: limits, paths, request and response schemas, error codes, field rules, the specs of the MCP tools and CLI commands, and the agent guide, written once and rendered for the MCP server, the Claude skill and the CLI	npm: `@fortrip/agent-contract`, from a `v*` tag on `main`, together with `fortrip`
`packages/cli`	The `fortrip` CLI: hotel search, live offers, orders and payment links from a shell, the local MCP bridge (`fortrip mcp`) and the agent guide (`fortrip guide`)	npm: `fortrip`, from a `v*` tag on `main`, together with `@fortrip/agent-contract`
`plugins/claude`	Claude plugin (hosted MCP server + static skill, generated)	Submitted in the developer portal; `.claude-plugin/marketplace.json` at the root lets Claude Code add this repo as a marketplace
`plugins/openai`	ChatGPT / Codex plugin	Zip uploaded in the OpenAI portal
`plugins/registry`	MCP Registry entry	The Publish Fortrip to MCP Registry workflow
`skills/fortrip-cli`	Skill for agents with a shell (generated)	`npx skills add FortripEngineering/fortrip --skill fortrip-cli` reads it from `main`
`scripts`	Repo-wide scripts: `generate.ts` renders the skills, `validate.mjs` checks the listings

Development

Node.js 22 or newer and pnpm 11.

pnpm install

pnpm test # tests of every package, and of the scripts pnpm generate # renders the skills from the contract pnpm generate --check # fails with a diff when a generated file is stale pnpm build && pnpm validate # checks the store listings

pnpm typecheck and pnpm build run for every package too. CI runs typecheck, tests and the build on Node.js 22 and 24, and on 24 also pnpm generate --check, pnpm validate and claude plugin validate --strict on ., plugins/claude and skills.

Generated files

The skills (SKILL.md and references/planning.md in plugins/claude/skills/fortrip and skills/fortrip-cli) and the contract's src/guide-data.generated.ts are generated. Never edit them: change the guide's fragments in packages/contract/guide/*.md (or a skill's front matter in scripts/generate.ts), run pnpm generate and commit the result. The fragments say which surface states what, and the Claude skill, the MCP instructions and the CLI's guide all render from them, so they cannot drift apart.

Publishing

Claude plugin

plugins/claude is a plugin with two parts:

.mcp.json points at the hosted MCP server. On claude.ai and in Cowork it shows up on the plugin's Connectors tab, where users sign in with their Fortrip account (OAuth); Claude Code connects to it directly.
skills/fortrip/ is the generated skill that tells Claude how to use the tools: call order, occupancy per room, prices and currency, confirming before the payment link, and errors. references/planning.md covers flexible dates, budgets, split stays and several destinations.

The skill is self-contained: the directory doesn't allow a plugin to fetch instructions at runtime (Software Directory Policy §2F), and its validator blocks unpinned npx launchers, so the CLI skill stays outside plugins/claude. pnpm validate fails if a file under it mentions npx, fortrip@latest or get_planning_guide.

Submit the plugins/claude folder in the developer portal. Check it with:

claude plugin validate --strict plugins/claude

claude plugin validate --strict .

The second command checks .claude-plugin/marketplace.json at the repository root. It lists plugins/claude as a plugin, which lets npx skills add find the plugin's skill next to skills/fortrip-cli, and lets Claude Code add this repository as a marketplace.

Claude Code keeps users on the version in plugin.json, so bump it whenever anything in plugins/claude changes, regenerated skill text included: patch for wording, minor for new behaviour or components, major for changes that break how people use it. The directory takes the listing icon from the first submission only.

CLI skill

skills/fortrip-cli is the CLI's guide as a static skill: the agent reads the commands, call order, sign-in and what to show the user before a payment link from the skill itself. It needs Node.js 22 or newer and isn't part of the Claude directory plugin.

npx skills add FortripEngineering/fortrip --skill fortrip-cli

OpenAI plugin

plugins/openai/plugin.json holds the listing copy and review test cases, and mcp.json the hosted server URL. mcp.json follows the Agent Plugins schema (type: streamable-http), while plugins/claude/.mcp.json follows Claude's (type: http); both point at the same server. Build the upload:

cd plugins/openai && rm -f ../../fortrip-openai.zip && zip -rX ../../fortrip-openai.zip plugin.json mcp.json assets

Upload the zip in the OpenAI portal. The portal verifies the domain through https://mcp.fortrip.ai/.well-known/openai-apps-challenge, served by mcp.fortrip.ai.

MCP Registry

plugins/registry/server.json lists Fortrip as io.github.FortripEngineering/fortrip, with two ways to connect: the hosted server (remotes) and the npm package fortrip, run as fortrip mcp (packages; the mcpName in packages/cli/package.json must equal the entry's name). The entry is published by its own workflow, Publish Fortrip to MCP Registry (.github/workflows/publish-mcp-registry.yml), which runs only from main and waits for a human to approve the mcp-registry environment. To publish a change, bump version (a version can't go down), set packages[].version to the CLI version on npm, merge to main and run the workflow. After a CLI release, run it once npm has the new version.

To deprecate an old version, or make it active again, run Set an MCP Registry version's status (.github/workflows/mcp-registry-status.yml) with the version, the status and, when deprecating, a message (the publisher takes none for active). It has the same main-only, approval-gated setup. A personal mcp-publisher login github can't do this: it only gets io.github. /*, so the org namespace comes through this repository's OIDC identity.

The Registry binds the server URL to one name, so a rename means deleting the old entry before publishing the new one.

Releasing

fortrip and @fortrip/agent-contract are released together, at the same version.

In a PR, set version to the new X.Y.Z in both packages/cli/package.json and packages/contract/package.json (npm version X.Y.Z --no-git-tag-version in each package's directory), set packages[].version in plugins/registry/server.json to it too, and run pnpm generate and commit what it changes. Merge the PR into main once CI passes.
Tag the merge commit on main and push the tag:

   git checkout main && git pull

git tag vX.Y.Z && git push origin vX.Y.Z

A human approves the npm-publish environment. The workflow publish.yml then publishes both packages to npm through trusted publishing (npm's OIDC sign-in from GitHub Actions, so no npm token is stored in GitHub), which gives them provenance.
Once npm has the new version, run the MCP Registry workflow (above).

The workflow refuses a tag that isn't vX.Y.Z or vX.Y.Z-rc.N, that differs from the version in either package.json, or that isn't on main. Its build job runs typecheck, tests and the build and packs both tarballs; its publish job, in the npm-publish environment, publishes those tarballs (@fortrip/agent-contract first) without installing or building anything. A release candidate, tagged vX.Y.Z-rc.N, is published under the next dist-tag, so npm install doesn't pick it up. Rerunning the publish job after a partial publish skips what is already on npm.

Docs

packages/docs is the Fumadocs site behind docs.fortrip.ai.

pnpm --filter ./packages/docs dev   # local dev server

pnpm --filter ./packages/docs test # its tests

Production docs follow the live server, not main. A docs deploy is a docs-* tag, and the order is:

Tag vX.Y.Z (npm, see Releasing above).
Ship the server release that pins that contract to production.
Push the tag docs-X.Y.Z.
A human approves the docs-production environment. The workflow deploy-docs.yml then builds and deploys to Vercel.

The workflow refuses to deploy unless all of these hold at the tagged commit:

the contract's version is a plain X.Y.Z, not an rc;
packages/contract/src is unchanged since the tag vX.Y.Z of that version;
the changelog has the version's entry, dated, and no entry says "Not released yet.".

The tag name itself is free-form. So once main has moved on from the live release (contract changes, or a new undated changelog entry), a docs deploy can't go out from main: cut a short branch from the live v* tag, make the docs-only fix there, tag docs-X.Y.Z- on that branch and push the tag, and also merge the fix to main. A docs-only fix needs no npm release and no changelog entry.

Before tagging a stable release, replace the version's "Not released yet." with "Released YYYY-MM-DD." in packages/docs/content/docs/changelog.mdx, or the changelog gate fails.

One-time setup, by the owner:

A Vercel project with Root Directory packages/docs, framework Next.js, "Include files outside the root directory" left on (the build reads packages/contract and packages/cli/package.json) and preview deployments on. packages/docs/vercel.json turns off Git deployments of main: production would otherwise follow main and skip the approval. Other branches still get previews. On the first real run, confirm a push to main creates no production deployment. Importing the project deploys main once anyway; the first docs-* deploy replaces it.
The docs.fortrip.ai domain on that project, and Vercel Analytics enabled.
The GitHub environment docs-production, with the same required reviewers as `np

Only the beginning is shown; read the rest in the repo

Fortrip

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Fortrip

Using Fortrip

Layout

Development

Generated files

Publishing

Claude plugin

CLI skill

OpenAI plugin

MCP Registry

Releasing

Docs