Connect Muse to Traveler.md

Muse is Meta’s assistant, available at muse.ai, on iOS and Android, and in WhatsApp. Muse can create a custom connector for a service that is not in its connector directory. After connecting, Muse can read your Traveler.md and Trip.md files and keep them updated as you plan.

Before you start

• Muse has a directory of connectors that Meta reviews, under Settings → Connectors. Traveler.md is not in that directory. You ask Muse to create a custom connector instead.
• Muse has no settings form for custom connectors and no MCP (Model Context Protocol) menu. You ask Muse in the conversation.
• Muse’s computer runs in Meta’s cloud, so the MCP server must be reachable over the public internet. Traveler.md’s server is public.

Steps

1. Start a conversation with Muse and send a message that gives the service name, the MCP server URL, and what you want Muse to do. For example:

   Text

   Create a custom connector for Traveler.md, my travel memory. It is a remote MCP server over streamable HTTP at https://mcp.traveler.md/mcp. It uses OAuth 2.1 with PKCE, and the OAuth endpoints are discoverable from the server, so sign in with my Traveler.md account instead of an API key. I want you to read my travel profile and my trips, and update them when I ask.

   The server URL is:

   MCP server URL

   https://mcp.traveler.md/mcp

2. Muse asks whether the server is reachable over HTTP and how it authenticates. Answer that it is a hosted HTTPS server that uses OAuth.

3. When Muse opens the Traveler.md sign-in page, sign in and approve the scopes. If Muse asks for a credential, enter it in Muse’s separate credential prompt, and never in the chat. Muse keeps credentials in its Secure Credentials Store.

4. Muse builds and tests the integration, then saves it as a reusable skill. The connector then appears under Settings → Connectors.

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

   Send this to Muse:

   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.

For the list of tools the connector can call, see Tools.

Good to know

• Meta does not review custom connectors. Meta does not check how a custom connector uses your information, and tells you to grant access with caution. Traveler.md’s write tools only ever touch your own profile and your own trips.

Troubleshooting

• Muse asks for an API key or a header? Tell Muse to use the OAuth sign-in instead. Traveler.md does not issue API keys. The OAuth sign-in can take more back-and-forth with Muse than a key does.
• Revoked or narrowed a connection and the assistant still has access? Changes take effect within a minute.
• Other issues: see Support.