Connect Claude to Traveler.md

Traveler.md is an official Claude Connector, available in Claude’s Connector Directory. Connect it so Claude 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). No server URL or custom configuration needed: if you have a Claude account, you’re a few clicks away.

The fastest path: the button below opens Traveler.md’s page in the Connector Directory on claude.ai, where you click Connect and sign in, skipping the settings navigation entirely.

In this guide:

• Claude on the web (claude.ai)
• Claude Desktop (and Cowork)
• Claude on mobile (iOS and Android)

Before you start

• You’ll need a Traveler.md account. If you don’t have one yet, you can create it during the connect flow.
• On Team and Enterprise plans, an Owner or Primary Owner enables the connector for the organization. Open Organization settings → Connectors, click Browse connectors, select Traveler.md, and click Add to your team. Each member then connects and authenticates individually.
• Enterprise plans can also use Enterprise-managed auth (beta), where the organization authorizes a connector once and members inherit access on first login.
• Claude connects to the Traveler.md server from Anthropic’s cloud, not your device, which is why connecting once makes Traveler.md available everywhere you sign in to Claude.

Claude on the web (claude.ai)

Click here to open Traveler.md directly in the Connector Directory:

Or navigate to it yourself:

1. In the left-hand navigation, click Customize, then Connectors.

2. Click the + button next to Connectors, then Browse connectors.

3. Search for Traveler.md and click Connect.

4. Sign in to your Traveler.md account, or create one. Once you authenticate, you’ll return to Claude with the connector active.

5. Send the prompt below to Claude, or add it to your custom instructions.

   Send this to Claude:

   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 trip file as soon as I mention somewhere I'd like to go, even loosely, with status Dreaming. Store the itinerary and ideas in it, and update it as plans firm up. - Ask before archiving. Check with me before you archive a trip. - 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.

Claude Desktop (and Cowork)

1. In the left sidebar, click Customize, then Connectors.

2. Click the + button next to Connectors, then Browse connectors.

3. Search for Traveler.md and click Connect.

4. Sign in to your Traveler.md account, or create one. A browser window opens so you can authenticate; once you do, you’re connected.

5. Send the prompt below to Claude, or add it to your custom instructions.

   Send this to Claude:

   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 trip file as soon as I mention somewhere I'd like to go, even loosely, with status Dreaming. Store the itinerary and ideas in it, and update it as plans firm up. - Ask before archiving. Check with me before you archive a trip. - 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.

Cowork uses the same connector; once Traveler.md is connected to your account it’s available to Cowork as a tool.

Claude on mobile (iOS and Android)

Traveler.md may not appear when you search the connector directory inside the mobile app. The connector lives on your Claude account, not the device, so connect on the web once and it comes with you to mobile. The fastest way from your phone is to open the Traveler.md connector page  in your browser, tap Connect, and sign in.

1. Connect Traveler.md using the link above, or the web or desktop steps. You only do this once.

2. Open the Claude app on your phone and sign in to the same account.

3. In a chat, tap the + button and enable Traveler.md for that conversation.

4. Send the prompt below as your first message if you want the assistant to use your files proactively.

   Send this to Claude:

   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 trip file as soon as I mention somewhere I'd like to go, even loosely, with status Dreaming. Store the itinerary and ideas in it, and update it as plans firm up. - Ask before archiving. Check with me before you archive a trip. - 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.

If you don’t see Traveler.md on mobile, confirm you connected it on web or desktop first and that you’re signed in to the same account.

Try it

Ask Claude: “What do you know about my travel preferences?” If everything’s wired up, Claude reads your Traveler.md and summarizes it. A brand-new account has an empty file, so just tell Claude 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

• Stuck on the OAuth page? See the connection debugging guide.
• Worked yesterday, not today? Your token may have expired or been revoked; re-authenticate from the connected-apps page.
• Revoked or narrowed a connection and the assistant still has access? Changes take effect within a minute.
• Other issues: see Support.