Connect Perplexity to Traveler.md

Perplexity supports custom remote connectors on Pro, Max, and Enterprise plans. You can add Traveler.md as a custom connector yourself so Perplexity can read your Traveler.md and Trip.md files and keep them updated.

Before you start

• Custom remote connectors require a Pro, Max, or Enterprise plan.
• The connector’s MCP server must use HTTPS (Traveler.md’s does).
• Connectors can be account-level (just you) or organization-scoped. Only admins can share a connector org-wide, and an admin must enable custom connectors for the organization first.

Steps

1. Open Account settings and click Connectors (or All settings).

2. Click + Custom connector (top-right), then select Remote.

3. Fill in the form:

   • Name: Traveler.md

   • MCP Server URL (HTTPS required):

     MCP server URL

     https://mcp.traveler.md/mcp

   • Description: optional

   • Authentication: OAuth

   • Transport: Streamable HTTP

4. Check the acknowledgement box and click Add.

5. Click the connector card to start the authorization flow, sign in to Traveler.md, approve the scopes, and enable it.

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

   Send this to Perplexity:

   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.