Connect Grok to Traveler.md

Grok (xAI) supports bring-your-own-MCP (Model Context Protocol), so you can add Traveler.md as a custom connector yourself, without waiting on an official listing. You can connect Grok on grok.com, Grok Bot (xAI’s always-on agent), or Grok Build (xAI’s agent for the terminal). After connecting, Grok can read your Traveler.md and Trip.md files and keep them updated as you plan.

In this guide:

• Option A: Grok connector (grok.com)
• Option B: Grok Bot
• Option C: Grok Build

Before you start

• Your MCP server must be reachable over the public internet. Traveler.md’s server is public.
• Business and Enterprise workspaces may require an admin to provision connectors in the workspace console. Check with your admin if you don’t see the option.

Option A: Grok connector (grok.com)

1. Go to grok.com/connectors .

2. Click New Connector, then select Custom.

3. Paste the URL below and complete the authentication step when prompted.

   MCP server URL

   https://mcp.traveler.md/mcp

4. Authorize your Traveler.md account, granting the scopes. Grok then discovers the tools the server exposes and makes them available in conversation.

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

   Send this to Grok:

   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.

Option B: Grok Bot

Grok Bot runs on its own cloud computer. The desktop and mobile apps are clients for chat and approvals, and the Bot can run routines on a schedule. Grok Bot is in beta. It is included with SuperGrok plans and with Cursor Pro and Teams plans.

Grok Bot has no settings form for custom MCP servers. You add a server from a Bot conversation.

1. Send the Bot this message:

   Text

   Add a custom MCP server called Traveler.md at https://mcp.traveler.md/mcp

2. The Bot repeats the name and URL back to you. Check them, then click Add it.

3. The Bot shows a connect card, because Traveler.md uses OAuth. Click Authorize, sign in to Traveler.md in the browser, and approve the scopes. The OAuth tokens stay on the connector backend. The Bot calls the tools without receiving the tokens.

4. In a chat, type @ and pick Traveler.md to attach the server. Then ask something that needs your files, for example “What do you know about my travel preferences?”

5. Paste the instruction block below into the Bot’s instructions.

   Send this to Grok Bot:

   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.

Grok Bot runs in the cloud, so it can only reach MCP servers on the public internet. Traveler.md’s server is public, so you do not need a tunnel.

Grok Bot on a team

Grok Bot uses the team’s Cursor connector policy. There is no separate connector list for Grok Bot. Connectors appear as plugins in the app.

• Admins choose which servers members can use in the Team Marketplace, on the Plugins & MCPs page of the dashboard.
• A connector that an admin blocks shows as Disabled by team admin.
• An MCP allowlist is available on Enterprise plans only.

Option C: Grok Build

Grok Build is xAI’s coding agent for the terminal. It connects to Traveler.md from your own machine and signs in with OAuth in your browser.

Install the Agent Plugin

The Traveler.md Agent Plugin  installs the server together with skills that teach Grok how to use it: read before you write, how a section is replaced rather than appended to, and how to recover from each error the server returns.

grok plugin install TravelAiSolution/traveler-md-agent-plugin

Run grok inspect and check that traveler-md lists 7 skills and 1 MCP server.

Or add the server on its own

To add only the server, without the skills:

grok mcp add travelermd https://mcp.traveler.md/mcp

This writes to ~/.grok/config.toml, so Traveler.md is available in every project. Add --scope project to write .grok/config.toml in the current directory instead.

Sign in

1. Start grok. The first time Grok calls a Traveler.md tool, it opens the sign-in page in your browser. To sign in before that, type /mcps, select travelermd, and press i.

2. Sign in to your Traveler.md account and approve the scopes. Grok stores the token on your machine. TravelAI does not.

3. Ask something that needs your files, for example “What do you know about my travel preferences?”

4. If you installed the plugin, its skills already cover how to use the tools. If you added the server on its own, paste the instruction block below into an AGENTS.md file:

   Send this to Grok Build:

   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.

Sign in from an interactive grok session first. A one-shot grok -p run cannot open the browser sign-in, so it reports that the server needs authentication.

Troubleshooting

• Revoked or narrowed a connection and the assistant still has access? Changes take effect within a minute.
• Traveler.md shows as “Disabled by team admin” in Grok Bot? Ask a team admin to allow it on the Plugins & MCPs page of the dashboard.
• Grok Bot asks for an API key or a header? Choose the sign-in option instead. Traveler.md only issues OAuth tokens through the sign-in flow.
• Grok Build lists the plugin’s skills but no MCP server? Run grok plugin update. Plugin versions before 1.3.1 installed the skills without the server.
• Grok Build shows a travelermd server you didn’t add? Grok Build also loads MCP servers from Claude Code and Cursor configuration. grok inspect shows where each server comes from.
• Other issues: see Support.