Connect Mistral Vibe to Traveler.md

Mistral Vibe supports custom MCP connectors. Add Traveler.md so Vibe can read your Traveler.md and Trip.md files and keep them updated.

Mistral renamed Le Chat to Vibe in mid-2026. If your account still shows the Le Chat name, the steps below are the same.

Before you start

• Adding a custom connector is an administrator action. On Free, Pro, and Student plans the account owner is the administrator by default, so if the workspace is yours you can do this yourself. On team plans, ask an administrator.
• The server must be HTTPS with a valid certificate and use the Streamable HTTP transport. Traveler.md’s is and does.

Steps

1. Open the Connectors page. Connectors live under Work, and once added they are reusable elsewhere in Vibe.

2. Click + Add Connector and switch to the Custom MCP Connector tab.

3. Enter:

   • Connector name: travelermd (no spaces or special characters)

   • Server URL:

     MCP server URL

     https://mcp.traveler.md/mcp

   • Description: optional

4. Click Connect. Vibe detects the authentication method and prompts you through the OAuth flow; sign in to Traveler.md and approve the scopes.

5. Review what the connector may do without asking. Vibe lets you set Always allow per function, so you can leave read_profile, read_trip, and list_trips on automatic and keep the writes behind a confirmation.

6. Paste the instruction block below into Vibe’s custom instructions, or send it as your first message.

   Send this to Vibe:

   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.

Troubleshooting

• Scope or revocation change not reflected? Changes can take up to 15 minutes to propagate. The app keeps its current token until then, and picks up the change immediately if it re-authenticates.
• Other issues: see Support.