Connect your AI assistant

Works on Claude for web, desktop and mobile. You don't need to edit a config file, and you don't need an API key.

1. Sign up at aitrips.io if you haven't already.
2. In Claude, open Settings and find Connectors, then choose to add a custom connector.
3. Paste https://www.aitrips.io/api/ai/mcp as the remote MCP server URL and save.
4. Claude sends you to aitrips.io to sign in and approve access. Approve it, and you land back in Claude with the tools available.

Access is granted per account through OAuth, so you can revoke it from Claude at any time without touching your aitrips.io password.

Same flow, different menu. Requires a plan that allows custom connectors.

1. Open Settings in ChatGPT and find Connectors.
2. Add a connector using the URL https://www.aitrips.io/api/ai/mcp.
3. Sign in to aitrips.io when prompted and approve access.

Deep research mode works too: the server exposes search and fetch so ChatGPT can look across your trips and pull the full record behind any result.

Any client that speaks MCP over streamable HTTP can connect. Point it at the same URL. OAuth discovery and dynamic client registration are both wired up, so a well-behaved client needs nothing else from you.

Claude Code:

claude mcp add --transport http aitrips https://www.aitrips.io/api/ai/mcp

Run /mcp inside Claude Code to complete the sign-in.

Prefer the connector flow above where you can. An API key is the fallback for scripts and for clients that can't run an OAuth flow.

1. Generate a key in Settings. Keys start with tpk_ and are shown once.
2. Send it as a bearer token on every request, or in an X-API-Key header.

The endpoint speaks JSON-RPC. Listing the tools is the quickest way to check a key works:

curl -X POST https://www.aitrips.io/api/ai/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Calling a tool uses tools/call with the tool name and its arguments:

curl -X POST https://www.aitrips.io/api/ai/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "trip_create",
      "arguments": {
        "name": "Tokyo Adventure",
        "destination": "Tokyo, Japan",
        "startDate": "2026-09-15",
        "endDate": "2026-09-22",
        "currency": "JPY",
        "timezone": "Asia/Tokyo"
      }
    }
  }'

Android gets a share-sheet entry for free through the PWA. On iOS, add the pre-built Shortcut below — it asks for your own API key on import, so there's nothing to build.

1. Generate an API key in Settings if you don't have one yet.
2. Open this iCloud link on your iPhone or iPad and tap Add Shortcut — it prompts for your API key during setup.
3. That's it. It appears next to Messages and Mail whenever you share a link or selected text.

The same request from any other client (curl, another Shortcut, an automation tool):

curl -X POST https://www.aitrips.io/api/ideas \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/somewhere-to-go", "boardLabel": "Shared"}'

Once connected, talk to it normally. It works out which tools to use.

• Plan me three days in Kyoto and put the walking routes on the map.
• Add a train from London Paddington to Oxford on the 14th, leaving around 9am.
• Review my Tokyo trip and tell me what's missing.
• Share the Kyoto trip with Maya as an editor so she can add restaurants.
• Make my Kyoto trip public so I can share a read-only link with no account needed.
• What did I save near Shibuya? Anything within a kilometre of the station.

Every tool checks your permissions on the trip it touches, and every one that deletes something is annotated so your assistant can warn you first.

• Free accounts get a daily cap on assistant requests. Pro removes it. See pricing.
• Your assistant can only reach trips you own or have been invited to, at the access level you were given.
• We store the trip data you create and a per-day request count. We don't store your conversations. See the privacy policy.
• Something not working? Get in touch.