Back to Home

Connect your AI assistant

Bring Claude, ChatGPT, or any MCP-compatible assistant to your trips. It gets 37 tools for building an itinerary, adding routed transport, and sharing the plan. Everything it writes appears in the browser straight away, and everything you change in the browser is visible to it.

Setup takes about two minutes and needs one thing: this URL.

https://www.aitrips.io/api/ai/mcp

Claude

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.

ChatGPT

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.

Claude Code and other MCP clients

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.

API keys, for clients without OAuth

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"
      }
    }
  }'

What to ask it

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.
  • What did I save near Shibuya? Anything within a kilometre of the station.

The 37 tools

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.

Trips

  • trip_createCreate a trip with dates, destination, budget, timezone
  • trip_getRead one trip with its items, locations and itinerary
  • trip_listList your trips, optionally filtered by status
  • trip_updateChange dates, destination, budget or status
  • trip_deleteDelete a trip and everything attached to it
  • trip_cloneCopy a trip, shifting every date to a new start

Itinerary items

  • trip_item_addAdd an activity, meal, accommodation or flight
  • trip_item_listList items by type, status or date range
  • trip_item_updateChange details, status or booking reference
  • trip_item_deleteRemove an item

Transport and routing

  • trip_transport_addAdd a leg across 11 modes; both ends geocoded, route drawn
  • trip_item_repair_transportRecover missing origin coordinates from the item name

Trip review

  • trip_reviewReport gaps: missing transport, empty days, stale routes, stops with no pin

Tasks

  • trip_task_createCreate a reminder, optionally linked to an item
  • trip_task_listList tasks by status
  • trip_task_updateChange details, due date or priority
  • trip_task_completeMark a task done
  • trip_task_deleteDelete a task

Notes

  • trip_note_createWrite a markdown note, optionally pinned to a date
  • trip_note_listList notes, filtered by date
  • trip_note_updateEdit a note
  • trip_note_deleteDelete a note

Locations

  • trip_location_addSave a place with coordinates and a type
  • trip_location_listList saved places by type, city or country
  • trip_location_nearbyFind saved places within a radius of a point
  • trip_location_deleteRemove a saved place

Sharing and collaboration

  • trip_share_createCreate a Viewer or Editor link, with optional expiry and use limit
  • trip_share_listList a trip's share links
  • trip_share_revokeRevoke a share link
  • trip_collaborators_listSee who has access, and at what level
  • trip_collaborators_removeRemove someone's access

Discussion

  • trip_item_comment_addComment on an item, with @mentions
  • trip_item_comment_listRead an item's comment thread
  • trip_item_voteVote an idea up or down

History

  • trip_activity_listWho changed what, and when

Search

  • searchSearch across trips, items and locations
  • fetchRead the full record behind a search result

Limits and privacy

  • 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.