Installation

Pick the connection that fits your client. Each one uses the same Fortrip account and returns the same data.

Agent skillCopy Anchor Link

For Codex, Claude Code, Muse, WorkBuddy and other agents that use skills and can run shell commands.

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

The skill carries the agent guide: when to use Fortrip, the call order, how to sign in, and what to show the user before they pay. Your agent runs the CLI with npx -y fortrip@latest; fortrip guide prints the same guide.

CLICopy Anchor Link

Needs Node.js 22 or newer. Run it with npx, or install it globally:

npm install -g fortrip

The package and the command are both fortrip. Its source is at https://github.com/FortripEngineering/fortrip. See the CLI reference.

Remote MCPCopy Anchor Link

Nothing to install. Use a client that supports Streamable HTTP and MCP OAuth.

• Endpoint: https://mcp.fortrip.ai/
• Transport: Streamable HTTP
• Authentication: OAuth sign-in with a Fortrip account. No API key.
• Listed in: the MCP Registry as io.github.FortripEngineering/fortrip, and Glama

A 401 before you sign in is expected: authenticate through your client.

Set up your clientCopy Anchor Link

Claude Desktop runs the local server; the others connect to the remote one.

CodexCopy Anchor Link

codex mcp add fortrip --url https://mcp.fortrip.ai/
codex mcp login fortrip

1. Run the first command to add the server.
2. Run the second and approve access in your browser.
3. Start a new conversation and ask for a stay.

Claude CodeCopy Anchor Link

claude plugin marketplace add FortripEngineering/fortrip
claude plugin install fortrip@fortrip

1. Run both commands. The plugin adds this server and Fortrip's skill.
2. Start a new session, run /mcp and sign in to Fortrip in your browser.
3. Ask for a stay.

To add only the server, run claude mcp add --transport http fortrip https://mcp.fortrip.ai/.

CursorCopy Anchor Link

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

1. Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project.
2. Open Cursor's MCP settings and sign in to Fortrip in your browser when Cursor asks.
3. Enable Fortrip's tools, then ask for a stay in Agent mode.

Claude DesktopCopy Anchor Link

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

1. Run npx -y fortrip login in a terminal and approve in your browser. The bridge needs Node.js 22 or newer and uses this sign-in.
2. In Claude Desktop, open Settings from the Claude menu, then Developer → Edit Config, and add this to claude_desktop_config.json.
3. Quit Claude Desktop completely, start it again and ask for a stay.

The bridge also starts before you sign in: a tool call then answers with how to sign in, and works once you have, without a restart.

claude.aiCopy Anchor Link

https://mcp.fortrip.ai/

1. Go to Customize → Connectors, click + Add, then Add custom connector.
2. Name it Fortrip, enter this URL and click Continue. Keep the detected sign-in settings (OAuth) and click Add.
3. Connect Fortrip, sign in to Fortrip in your browser and ask for a stay.

On Team and Enterprise plans, an Owner adds the connector under Organization settings → Connectors (Add, then Custom → Web); members then connect it from Customize → Connectors.

ChatGPTCopy Anchor Link

https://mcp.fortrip.ai/

1. In ChatGPT's settings, turn on developer mode. On a workspace, an admin may need to allow it.
2. Create an app with this URL and OAuth authentication, and sign in to Fortrip in your browser when ChatGPT asks.
3. Turn the app on in a conversation and ask for a stay.

Local MCPCopy Anchor Link

For clients that launch local commands. The CLI runs a stdio server that forwards to the hosted server, so there is nothing else to install. It uses the CLI's sign-in, so run npx -y fortrip login first. Then add it to your client:

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

Configure either the remote or the local server in a client, not both. See fortrip mcp.

AuthenticationCopy Anchor Link

Both use a Fortrip account and the same OAuth service. When a CLI command needs a sign-in it does not wait: it exits with code 3 and normally prints a loginUrl and a userCode (a rejected FORTRIP_TOKEN prints tokenSource and no link). An agent can give both to the user and rerun the command once they have approved.