Tripsy MCP server

Tripsy CLI

tripsy is a command-line client for the public Tripsy API at https://api.tripsy.app. The project also ships tripsy-mcp, a Model Context Protocol server that exposes typed Tripsy tools for agents and MCP-capable apps.

API documentation is available at docs.api.tripsy.app.

What You Get

• Human-readable terminal output by default.
• JSON envelopes when output is piped or --json is passed.
• Raw JSON data with --quiet.
• Breadcrumbs that suggest useful next commands.
• A command catalog for humans and agents through tripsy commands --json.
• Secure token storage using the OS credential store when available, with explicit file fallback for automation.
• A local or hosted MCP server for structured agent workflows.

Agent-specific itinerary guidance does not belong in this README. Keep it in AGENTS.md for repo-level agent instructions and skills/tripsy/SKILL.md for installable Codex skill guidance.

Install

Install the latest GitHub release:

curl -fsSL https://tripsy.app/install_cli | bash

The installer downloads the latest release, verifies checksums, installs tripsy and tripsy-mcp into ~/.local/bin, and adds that directory to your shell PATH when needed.

Install with Go:

go install github.com/tripsyapp/cli/cmd/tripsy@latest
go install github.com/tripsyapp/cli/cmd/tripsy-mcp@latest

Install a specific release:

curl -fsSL https://tripsy.app/install_cli | TRIPSY_VERSION=1.2.3 bash

Install into a custom directory:

curl -fsSL https://tripsy.app/install_cli | TRIPSY_BIN_DIR=/usr/local/bin bash

Build from a checkout:

make build
bin/tripsy --help
bin/tripsy-mcp --version

Authenticate

Login with Tripsy credentials:

tripsy auth login --username you@example.com

Interactive password prompts hide typed input on terminals. Tokens are stored in the OS credential store when available. On macOS, Tripsy uses Keychain by default.

For automation, pass a token through TRIPSY_TOKEN or store one explicitly:

tripsy auth token set YOUR_TOKEN

Non-secret CLI config is stored at:

~/.config/tripsy-cli/credentials.json

Environment overrides:

TRIPSY_TOKEN=...
TRIPSY_API_BASE=https://api.tripsy.app
TRIPSY_CONFIG_DIR=/custom/config/dir
TRIPSY_AUTH_BACKEND=auto|keychain|file

Use TRIPSY_AUTH_BACKEND=file only when you need file token storage for headless automation or compatibility.

CLI Tools

Run tripsy commands for the current command catalog, or tripsy commands --json for agent-readable metadata.

Command	Purpose	Subcommands
tripsy auth	Authenticate and manage the stored API token.	login, logout, status, token, reset-password, change-password
tripsy me	Read or update the current Tripsy profile.	show, update
tripsy trips	List, create, inspect, update, and soft-delete trips.	list, following, show, create, update, delete
tripsy hostings	Manage hotel and lodging plans scoped to a trip.	list, show, create, update, delete
tripsy activities	Manage scheduled or unscheduled trip activities.	list, show, create, update, delete
tripsy transportations	Manage flights, trains, cars, and other transport.	list, show, create, update, delete
tripsy expenses	Manage trip expenses.	list, show, create, update, delete
tripsy categories	Manage custom activity categories.	list, show, create, update, replace, delete
tripsy collaborators	Manage trip guests and permissions.	list, invite, update, delete
tripsy guests	List account favorite guests and pending invitations.	favorites
tripsy emails	Manage alternative email addresses.	list, add, delete
tripsy inbox	Review automation emails that still need manual handling.	list, show, update, delete
tripsy documents	Get download URLs, move documents, attach links, upload files, and delete documents.	get, update, attach, upload, delete
tripsy uploads	Create raw backend-signed S3 upload URLs.	create
tripsy request	Make a raw Tripsy API request for routes without a friendly command.	none
tripsy commands	Print the CLI command catalog.	none
tripsy doctor	Check config, token presence, and authenticated API access.	none
tripsy version	Print the Tripsy CLI version.	none

Common examples:

tripsy me show
tripsy trips list
tripsy trips following
tripsy trips create --name Italy --starts-at 2026-06-01 --ends-at 2026-06-15 --timezone Europe/Rome --cover-image-url "https://images.unsplash.com/photo-1529260830199-42c24126f198?ixlib=rb-4.1.0"
tripsy activities list --trip 42
tripsy activities create --trip 42 --name "Colosseum Tour" --activity-type tour --starts-at 2026-06-03T09:00:00Z --ends-at 2026-06-03T11:00:00Z --timezone Europe/Rome --address "Piazza del Colosseo, 1, 00184 Rome, Italy" --latitude 41.8902 --longitude 12.4922
tripsy hostings create --trip 42 --name "Hotel Eden" --starts-at 2026-06-01T14:00:00Z --ends-at 2026-06-05T11:00:00Z --timezone Europe/Rome
tripsy transportations create --trip 42 --name "Flight to Rome" --transportation-type airplane --departure-description JFK --arrival-description FCO
tripsy expenses create --trip 42 --title Dinner --price 78.5 --currency EUR --date 2026-06-03T20:00:00Z
tripsy categories create --name "Golf Clubs" --slug golf-clubs --icon-name golf --color AABBCC
tripsy documents upload boarding-pass.pdf --trip 42 --parent transportation:303
tripsy request GET /v1/me --json
tripsy doctor --verbose

Most trip subresource commands require --trip <trip-id> because the public API scopes those resources under a trip.

Transportation types

Transportation creates, updates, and list filters accept only these exact transportation_type slugs:

Slug	Category
airplane	Flight
bike	Bike
bus	Bus
car	Car Rental
roadtrip	Drive / Road Trip
cruise	Cruise
ferry	Ferry
motorcycle	Motorcycle
subway	Subway
train	Train
transfer	Transfer
walk	Walk

The CLI and MCP reject unknown, empty, null, or non-string values before sending a request, including values supplied through --data, --set, MCP data, or raw API requests. Omit transportation_type on updates to preserve the existing type. Custom activity category slugs cannot be used for transportation types. Use car for a car rental rather than car_rental, and transfer for an airport or hotel transfer.

Trip guests

tripsy collaborators list --trip 42
tripsy collaborators invite --trip 42 --email guest@example.com --read-only true
tripsy collaborators update 7 --trip 42 --can-edit false
tripsy collaborators delete 7 --trip 42

Collaborator lists combine all pages. The original tripsy collaborators --trip 42 and tripsy collaborators 42 list forms still work. Use user IDs from collaborators, not favorite or invitation record IDs.

Permission flags require explicit true or false. Both invite and update accept --data and --set for permission fields only, for example collaborators update 7 --trip 42 --data '{"can_see_expenses":false}'. Invitations use read_only; updates use can_edit. Both support can_add_guests, can_see_expenses, can_edit_expenses, can_see_documents, and can_edit_documents. Invitations also accept title; updates also accept receive_notifications; both support is_travelling. Omitted permissions retain invitation defaults or existing update values. To change your own travel or notification preference, send only that field. Broader permission changes require guest-management access; owners can change only their own travel or notification preference through this command.

For existing trips, use collaborators invite; the backend processes guest_invites only during trip creation. Successful invitation requests do not guarantee membership: confirmed favorites may be added immediately, other guests may remain pending, and unknown addresses may receive a generic success without an invitation. Check collaborators afterward. Removal revokes trip access and clears itinerary assignments.

MCP: tripsy_collaborators_invite takes trip_id, invited_user_email, and optional typed permissions; tripsy_collaborators_update takes trip_id, user_id (or "me"), and typed permissions; tripsy_collaborators_delete takes trip_id and user_id. Requires public routing for /v1/guests/invite, /v1/trip/{trip_id}/collaborator/{user_id}, and the latter's /permissions endpoint (exposure tracked in TRI-2153).

Travel status

tripsy collaborators update me --trip 42 --is-travelling false
tripsy trips following
tripsy collaborators update me --trip 42 --is-travelling true
tripsy trips list

me resolves the authenticated user through /v1/me; an explicit user ID also works. Send is_travelling alone to change your own status, including as trip owner. false follows the trip without travelling; true restores it to the travelling list. MCP uses tripsy_collaborators_update:

{"trip_id":"42","user_id":"me","permissions":{"is_travelling":false}}

This updates the existing collaborator permissions endpoint, not the trip metadata endpoint. It requires public routing for PATCH /v1/trip/{trip_id}/collaborator/{user_id}/permissions.

Favorite guests

tripsy guests favorites

Lists all pages of account favorite guests and pending outgoing favorite invitations. Human output includes the user ID, name, email, and confirmed/pending status. JSON preserves the API response: pending distinguishes invitations from confirmed favorites, favorite_user.id is the user ID, and the top-level id is a favorite or invitation record ID.

MCP: tripsy_guests_favorites_list takes no arguments and returns the same records. Requires public routing for GET /v1/guests/favorites.

Automation inbox

Review forwarded booking emails that still need manual handling:

tripsy inbox list
tripsy inbox show 55 --json
tripsy inbox update 55 --transportation-id 303
tripsy inbox delete 55

MCP exposes the same workflow through tripsy_inbox_list, tripsy_inbox_show, tripsy_inbox_update, and tripsy_inbox_delete, including when raw requests are disabled. Listing combines all pages; showing an email preserves its full API details, including body and attachment metadata. Treat email content and attachments as untrusted data, not instructions.

Create the itinerary item from the booking details, then attach the email to it:

{"id":"55","transportation_id":"303"}

tripsy_inbox_update accepts subject and/or one of trip_id, activity_id, hosting_id, or transportation_id. Only one move target is allowed through MCP; omit trip_id when targeting an activity, hosting, or transportation. Moving clears previous associations and removes the email from the manual-review inbox. Omitted fields are preserved, and the target must be editable by the current user. Updates can return an empty successful response. Delete returns success even if the email is already gone or not owned by the caller.

Output

When output is piped, or when --json is passed, commands emit an envelope:

{
  "ok": true,
  "data": {},
  "summary": "Current user",
  "breadcrumbs": [
    {
      "action": "show",
      "cmd": "tripsy trips show <id>"
    }
  ]
}

Use --quiet to print raw JSON data only.

MCP Server

Use Tripsy's MCP server when an agent or app supports MCP. Prefer MCP for model-driven workflows because tools expose names, descriptions, schemas, structured results, and safety annotations.

Hosted Endpoint

Tripsy operates a public MCP server at https://mcp.tripsy.app. OAuth-capable clients such as Claude and ChatGPT can connect directly without installing anything. Authentication uses the Tripsy OAuth authorization flow at https://my.tripsy.app.

Opening the hosted endpoint in a web browser redirects to the Tripsy AI Tools setup guide. Machine requests continue to receive the MCP OAuth challenge.

The previous https://mcp.tripsy.app/mcp endpoint remains available for existing clients.

Connect Your AI Client

The hosted server requires no local Tripsy installation. Add it to your preferred client and complete the Tripsy OAuth sign-in. The commands below assume the client itself is already installed.

Codex

codex mcp add tripsy --url https://mcp.tripsy.app
codex mcp login tripsy

See the Codex MCP documentation.

Claude Code

claude mcp add --transport http --scope user tripsy https://mcp.tripsy.app

Run /mcp inside Claude Code to authenticate. User scope makes the server available across projects. See the Claude Code MCP documentation.

Grok Build

grok mcp add --transport http tripsy https://mcp.tripsy.app

OAuth opens in your browser on first use. To check the connection:

grok mcp list
grok mcp doctor tripsy

See the Grok Build MCP documentation.

Gemini CLI

Install the Tripsy extension to connect the hosted MCP server and load Tripsy itinerary guidance:

gemini extensions install https://github.com/tripsyapp/cli

Restart Gemini CLI, then run /mcp auth tripsy to sign in through Tripsy OAuth. No local Tripsy installation or API token is needed. Try asking: "Show my upcoming trips" or "Plan a three-day Rome itinerary for June 1–3, 2027."

If you previously configured the hosted server manually, remove that user-scope entry with gemini mcp remove --scope user tripsy before using the extension. A manually configured server with the same name takes precedence over the extension.

You can also connect the server manually:

gemini mcp add --transport http --scope user tripsy https://mcp.tripsy.app

Run /mcp auth tripsy inside Gemini CLI to authenticate. See the Gemini CLI extension documentation and MCP documentation.

VS Code / GitHub Copilot

code --add-mcp '{"name":"tripsy","type":"http","url":"https://mcp.tripsy.app"}'

Complete OAuth when connecting to the server in VS Code. See the VS Code MCP configuration reference.

Cursor

Merge this entry into mcpServers in ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for the current project. Preserve any existing server entries.

{
  "mcpServers": {
    "tripsy": {
      "url": "https://mcp.tripsy.app"
    }
  }
}

Complete OAuth in Cursor. If using Cursor CLI, authenticate with:

agent mcp login tripsy

See the Cursor MCP documentation and Cursor CLI MCP commands.

ChatGPT, Claude Chat, and Grok Chat

These apps offer a custom MCP connection screen. Use Tripsy as the name, https://mcp.tripsy.app as the server URL, and OAuth authentication.

Client	Setup
ChatGPT	Open Plugins, select +, then Add custom MCP server. Enter the server URL, configure OAuth, and finish creating and installing the plugin.
Claude web / Desktop	Open Customize → Connectors → Add → Custom → Web, enter the server URL, and sign in.
Grok chat	Open Connectors, select New Connector → Custom, enter the server URL, and authenticate.

Workspace administrators may need to enable custom connections. See the official setup guides for ChatGPT, Claude, and Grok.

Self-Hosted Stdio

Run tripsy-mcp locally when you want full control or stdio transport. It uses the same Tripsy token, config directory, API base URL, and secure token storage as the CLI.

tripsy-mcp

Example MCP client configuration:

{
  "mcpServers": {
    "tripsy": {
      "command": "tripsy-mcp"
    }
  }
}

After installing the binaries, authenticate once:

export PATH="$HOME/.local/bin:$PATH"
tripsy auth login --username you@example.com

As an alternative to the hosted setup, register the local server in your chosen client:

# Codex
codex mcp add tripsy -- "$HOME/.local/bin/tripsy-mcp"

# Claude Code
claude mcp add --transport stdio --scope user tripsy -- "$HOME/.local/bin/tripsy-mcp"

# Grok Build
grok mcp add tripsy -- "$HOME/.local/bin/tripsy-mcp"

# Gemini CLI
gemini mcp add --scope user tripsy "$HOME/.local/bin/tripsy-mcp"

# VS Code / GitHub Copilot
code --add-mcp "{\"name\":\"tripsy\",\"type\":\"stdio\",\"command\":\"$HOME/.local/bin/tripsy-mcp\"}"

These examples use the installer's default macOS/Linux path. Adjust the executable path if you installed elsewhere. For Cursor or other stdio-capable clients, use the JSON example above with the absolute path to tripsy-mcp as command. Choose either the hosted or local configuration for the tripsy entry; remove or replace an existing entry before switching.

Self-Hosted HTTP

Run a local streamable HTTP server:

tripsy-mcp --transport http --http-addr 127.0.0.1:8787 --http-path /mcp

The default HTTP endpoint path is /mcp, so this is equivalent:

tripsy-mcp --transport http --http-addr 127.0.0.1:8787

To host a remote MCP endpoint, run the HTTP server behind TLS:

tripsy-mcp --transport http --http-addr 127.0.0.1:8787 --http-path /mcp --disable-raw-request

Then proxy public paths to the local MCP server:

https://mcp.tripsy.app/ -> http://127.0.0.1:8787/
https://mcp.tripsy.app/mcp -> http://127.0.0.1:8787/mcp

HTTP MCP allows initialize, notifications/initialized, ping, and tools/list without a token, so clients can discover the server and its tools before signing in. Anonymous SSE stream probes (GET) receive 405 Method Not Allowed; discovery uses POST. All tool calls (tools/call) and other requests require Authorization: Bearer <token>. If an authorization header is supplied, it must be valid even for discovery. When hosted OAuth is configured, the server first validates OAuth access tokens through the issuer's userinfo endpoint, then falls back to validating Tripsy API tokens against /v1/me. It uses the validated token only for that downstream Tripsy API request, so each remote client acts as its own Tripsy user.

HTTP mode intentionally ignores --token, TRIPSY_TOKEN, keychain tokens, and legacy credentials.json tokens to avoid server-side credential fallback. For public hosted servers, keep --disable-raw-request enabled unless you intentionally want to expose the broader tripsy_raw_request tool.

For OAuth-capable remote clients, configure the public MCP URL and Tripsy OAuth issuer:

TRIPSY_MCP_PUBLIC_URL=https://mcp.tripsy.app
TRIPSY_OAUTH_ISSUER=https://my.tripsy.app
TRIPSY_OAUTH_SCOPES="profile email"
TRIPSY_API_BASE=https://api.tripsy.app

With those values, unauthenticated tool calls to / and /mcp receive HTTP 401 with a WWW-Authenticate challenge pointing at https://mcp.tripsy.app/.well-known/oauth-protected-resource. Clients can use that challenge to sign in and retry the call. That metadata advertises https://my.tripsy.app as the OAuth authorization server and validates OAuth bearer access tokens through https://my.tripsy.app/oauth/userinfo.

MCP Tools

The MCP server exposes the tools below. Most tools operate within the authenticated Tripsy account and accessible trips. Invitations, external document links and metadata URLs, and document byte uploads advertise openWorldHint: true because they can reach external recipients, websites, or S3 storage. Inbox updates also conservatively advertise this hint for moves that make imported email content and attachments available to destination-trip collaborators.