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-plugins --skill fortrip-cliThe skill tells your agent to run npx -y fortrip@latest skill, which prints the current agent guide: when to use Fortrip, the call order, sign-in, and what to show the user before sharing a payment link. A new CLI release updates every installed skill.
CLI
Needs Node.js 22 or newer and has no runtime dependencies. Run it with npx, or install it globally:
npm install -g fortripThe 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 fortripRun 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/mcpRun 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; CLI tokens do not work with the remote server.
Local MCP
An open-source stdio server for clients that launch local commands. It reads the CLI's sign-in, so run npx fortrip login first.
git clone https://github.com/FortripEngineering/fortrip-mcp.git
cd fortrip-mcp
npm ci && npm run buildThen add it to your client with the absolute path to the checkout:
{
"mcpServers": {
"fortrip-local": {
"command": "node",
"args": ["/absolute/path/to/fortrip-mcp/dist/index.js"]
}
}
}Codex and Claude Code examples are in the repository README. Configure either the remote or the local server in a client, not both.
Authentication
| Connection | How it signs in |
|---|---|
| Skill, CLI, local MCP | npx fortrip login opens a browser to approve a device code. The token is saved to ~/.config/fortrip/credentials.json and expires after 90 days without use; sign in again after that. npx fortrip logout revokes it; you can also see and revoke CLI sign-ins on the Fortrip CLI page of your account. Set FORTRIP_TOKEN to use a token in CI or a sandbox. |
| Remote MCP | OAuth 2.1 with PKCE. Your client opens a Fortrip sign-in page and you approve access. |
Without a token, CLI commands exit with code 3 and print a loginUrl. An agent can give that link to the user and rerun the command once it is approved.