Connect VS Code to Traveler.md

Connect Traveler.md to VS Code so Copilot Chat can read your Traveler.md to personalize suggestions, read and update Trip.md files as you plan, and update Traveler.md when you tell it something new (with your confirmation). VS Code speaks the remote MCP streamable-HTTP transport, so setup is a URL plus a browser OAuth flow.

Before you start

• VS Code 1.102 or later, where MCP support became generally available.
• GitHub Copilot enabled. MCP tools run only in Copilot Chat’s Agent mode.

One-click install

The fastest path. Click to add Traveler.md to VS Code, then confirm the install in the prompt VS Code opens:

On Insiders, use this link instead. If your browser doesn’t hand either one to VS Code, open the install through vscode.dev, which redirects into the same flow.

Manual configuration

Alternatively, add Traveler.md yourself. Run MCP: Add Server from the Command Palette for a guided flow, or edit the config directly: .vscode/mcp.json in a project (that project only), or the file MCP: Open User Configuration opens (all projects). Add the travelermd entry:

{
  "servers": {
    "travelermd": {
      "type": "http",
      "url": "https://mcp.traveler.md/mcp"
    }
  }
}

VS Code’s key is servers, not the mcpServers other clients use. The rest of the entry is the same everywhere.

Authenticate

1. VS Code opens the OAuth consent flow in your browser. Sign in to your Traveler.md account and review the scopes, then approve. VS Code stores the token; TravelAI does not.

2. Open the Chat view and switch the mode dropdown from Ask to Agent. MCP tools are available only in agent mode.

3. Click Configure Tools and confirm the travelermd tools are listed and turned on.

4. Paste the instruction block below into your Copilot custom instructions (for example .github/copilot-instructions.md) or send it as your first message in a chat:

   Send this to VS Code:

   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.

Try it

Ask Copilot Chat in agent mode: “What do you know about my travel preferences?” If everything’s wired up, it calls the read_profile tool and summarizes your file. A brand-new account has an empty file, so just tell it how you travel (“I always pick aisle seats, I’m Hilton Honors Gold, I prefer boutique hotels”) and ask it to save them. It confirms before writing.

Troubleshooting

• Nothing happened when you clicked the install button? Your browser may not be registered to open vscode: links. Use the vscode.dev link above, or add the entry by hand with the JSON in the section above.
• Don’t see the tools? Check that the chat is in Agent mode, then open Configure Tools and make sure travelermd is enabled. Tools stay hidden in Ask mode even when the server is connected.
• 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. VS Code keeps its current token until then, and picks up the change immediately if you re-authenticate.
• Other issues: see Support.