Connect Notion to Traveler.md
Bring your travel memory into Notion. Connect Traveler.md as a custom MCP connection and Notion’s AI agents can read your Traveler.md profile and Trip.md files, so planning inside Notion starts with full context instead of a blank page. Custom MCP connections are a Business and Enterprise plan feature, and they’re added per Custom Agent.
Before you start
- A Traveler.md account. If you don’t have one yet, you can create it during the connect flow.
- A Notion workspace on a Business or Enterprise plan (custom connections are available on these plans).
- If you’re not a workspace admin, you’ll need one to complete step 1. This is a one-time setup for the whole workspace.
Steps
-
Enable custom connections (admin, one time). A workspace owner or admin opens Settings > Notion AI > AI connectors and turns on Enable Custom MCP servers. This only needs to happen once for your workspace.
-
Add Traveler.md to your agent. Open your Custom Agent’s settings and go to Tools & Access.
-
Click Add connection, then choose to add a custom server.
-
Enter the Traveler.md server URL:
MCP server URLhttps://mcp.traveler.md/mcp -
Follow the prompts to sign in to your Traveler.md account, or create one, and approve the scopes.
-
-
Choose what Notion can do. You’re always in control of your memory. In the connection settings, toggle individual tools on or off, and choose whether actions run automatically or ask for your confirmation first. Read access lets your agent personalize with your preferences; write access lets it update your trips as plans come together.
-
Paste the instruction block below into the agent’s instructions so Notion knows when to use your files.
Send this to Notion: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.
That’s it. Ask your agent something like “Plan a weekend trip that fits my travel style” and it will already know what that means.
Good to know
- Connections in Notion are per agent. If you use several Custom Agents, connect Traveler.md to each one you want to have travel context.
- You can disconnect anytime from the same Tools & Access settings.
Troubleshooting
- 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. The connection keeps its current token until then, and picks up the change immediately if it re-authenticates.
- Other issues: see Support.