Get started

Installation

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

Agent skill

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 sharing a payment link. Your agent runs the CLI with npx -y fortrip@latest; fortrip guide prints the same guide.

CLI

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. Source on GitHub. See CLI reference.

Remote MCP

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

Endpoint	`https://fortrip.ai/api/mcp`
Transport	Streamable HTTP
Authentication	OAuth sign-in with a Fortrip account. No API key.
Directory	Glama connector

Codex

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

Run the first command to add the remote server. Run the login command and approve access in your browser.

Claude Code

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

Run the command to add Fortrip to Claude Code. Open /mcp in Claude Code and follow the browser sign-in prompt.

Cursor

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

Add this server configuration to .cursor/mcp.json in your project. Open Cursor's MCP settings and follow the browser sign-in prompt.

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

Local MCP

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-local": {
      "command": "npx",
      "args": ["-y", "fortrip", "mcp"]
    }
  }
}

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

Authentication

Connection How it signs in

Skill, CLI, local MCP OAuth device flow. npx fortrip login prints a link and a code; open the link, sign in to Fortrip and approve, and the CLI saves the sign-in to ~/.config/fortrip/credentials.json. Access tokens last 24 hours and the CLI renews them itself; you stay signed in until npx fortrip logout, which signs out that machine only. For a sandbox or one CI run you can set FORTRIP_TOKEN to an access token instead; it lasts at most 24 hours.

Remote MCP OAuth 2.1 with PKCE. Your client opens a Fortrip sign-in page and you approve access.

Connection	How it signs in
Skill, CLI, local MCP	OAuth device flow. `npx fortrip login` prints a link and a code; open the link, sign in to Fortrip and approve, and the CLI saves the sign-in to `~/.config/fortrip/credentials.json`. Access tokens last 24 hours and the CLI renews them itself; you stay signed in until `npx fortrip logout`, which signs out that machine only. For a sandbox or one CI run you can set `FORTRIP_TOKEN` to an access token instead; it lasts at most 24 hours.
Remote MCP	OAuth 2.1 with PKCE. Your client opens a Fortrip sign-in page and you approve access.

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.