Connect Cursor to Traveler.md

Connect Traveler.md to Cursor so the assistant can read your Traveler.md to personalize suggestions, read and update Trip.md files as you plan, and update Traveler.md when you tell it something new (with your confirmation). Cursor speaks the remote MCP streamable-HTTP transport, so setup is a URL plus a browser OAuth flow.

One-click install

The fastest path. Click to add Traveler.md to Cursor, then confirm the install in the dialog Cursor opens:

If nothing happens, your browser may not be registered to open cursor:// links. Open the install through cursor.com instead, which hands the same configuration to Cursor.

Manual configuration

Alternatively, add Traveler.md to your MCP config yourself. Edit ~/.cursor/mcp.json (global, all projects) or .cursor/mcp.json in a project (that project only), and add the travelermd entry:

{
  "mcpServers": {
    "travelermd": {
      "url": "https://mcp.traveler.md/mcp"
    }
  }
}

Authenticate

1. Open Cursor Settings → MCP (or Tools & Integrations). You’ll see travelermd listed.

2. Cursor opens the OAuth consent flow in your browser. Sign in to your Traveler.md account and review the scopes, then approve. Cursor stores the token; TravelAI does not.

3. Back in Cursor, confirm travelermd shows as connected and its tools are enabled.

4. Paste the instruction block below into Cursor’s rules (Cursor Settings → Rules) or send it as your first message in a chat:

   Send this to Cursor:

   I use Traveler.md as my travel memory, so my preferences and my trips live in one place I can connect to the travel tools I use. There are two kinds of files, and I manage both on the Traveler.md platform: one profile with my lasting travel preferences, and one file per trip with the details for that trip. You can read and update both through the Traveler.md connector. Follow these rules whenever travel comes up: - Read before answering. For any travel-related request, first read my profile and the relevant trip file. Use what's there, and don't ask me for anything the files already contain. - If you can't reach my files, say so. Don't guess or invent preferences. Tell me the connector isn't responding so I can reconnect it. - Capture durable preferences immediately. When I state a lasting travel preference, even casually with no trip in progress (e.g. "I prefer aisle seats"), update my profile right away, then confirm in one line what changed. Make the actual update, don't just say you will. - Keep one-off details in the trip file. Needs specific to a single trip (e.g. "ground-floor room this time") go in that trip's file, not my profile. For that trip, the trip file overrides my general defaults. - One file per trip. Create a new trip file when a trip takes shape, store the itinerary and ideas in it, and update it as plans firm up. - Keep everything clean. No duplicates, and preserve existing entries unless you're correcting or replacing them. If a new preference conflicts with an old one, replace it and note the change. - Flag the edits that matter. Tell me briefly when you create a trip file or make a significant change, and skip announcing trivial ones.

Try it

Ask Cursor in the chat pane: “What do you know about my travel preferences?” If everything’s wired up, it calls the read_profile tool and summarizes your file. A brand-new account has an empty file, so just tell it how you travel (“I always pick aisle seats, I’m Hilton Honors Gold, I prefer boutique hotels”) and ask it to save them. It confirms before writing.

Troubleshooting

• Don’t see the tools? Make sure the server is toggled on under Cursor Settings → MCP and that OAuth completed. A red dot next to travelermd usually means the OAuth flow didn’t finish; click it to retry.
• Stuck on the OAuth page? See the connection debugging guide.
• Scope or revocation change not reflected? Changes can take up to 15 minutes to propagate. Cursor keeps its current token until then, and picks up the change immediately if you re-authenticate.
• Other issues: see Support.