Connect VS Code with GitHub Copilot

VS Code connects to Vessero through GitHub Copilot's chat, in VS Code 1.99 or later. Any Copilot plan works. On Copilot Business or Enterprise, an admin first turns on the MCP servers in Copilot policy. In Connected apps, the same steps open one at a time, with what to copy, and the last one tells you when VS Code is in.

Connect VS Code

1. Add the server. In VS Code, signed in to GitHub Copilot with a folder open, open the Command Palette (⇧⌘P on a Mac, Ctrl+Shift+P elsewhere) and run MCP: Add Server.
2. Choose HTTP (HTTP or Server-Sent Events).
3. Enter the URL https://vessero.com/mcp.
4. Enter the server ID vessero.
5. Pick Global, then Copilot Global.
6. Sign in to Vessero. Accept VS Code's prompt to trust the server, then its prompt to sign in.
7. Vessero's page opens in your browser. Sign in if it asks, then press Allow.
8. Start a new chat. Open the Chat view and select New Chat (+).
9. Check it works. Ask: "Use Vessero to show my credit balance."
10. Approve the tool call when Copilot asks, and it answers with your balance. Open the call to see it came from vessero.

Use a key instead

On a computer with no browser to sign in with, give VS Code an API key. Copilot reads it from your environment, so the key isn't written in its settings.

1. Add the server. In Connected apps, under Connect another app, press VS Code, then Use a key instead.
2. Name the key, choose what it can do and, if you like, give it a daily cap. Press Make the key.
3. Add the line export VESSERO_API_KEY="vsk_…" to ~/.zshrc or ~/.bashrc, with your key in place of vsk_….
4. Put the settings the page shows in ~/.copilot/mcp-config.json. They send the key as Bearer ${VESSERO_API_KEY}.
5. Restart VS Code, so it reads the key.
6. Start a new chat. Open the Chat view and select New Chat (+).
7. Check it works. Ask: "Use Vessero to show my credit balance."

If it doesn't connect

• It doesn't connect or sign in. Run MCP: List Servers, pick vessero and choose Show Output to read the error.
• No sign-in appears in a Copilot chat. Open a chat in the Local harness, which signs in itself.
• An old sign-in gets in the way. Run Authentication: Remove Dynamic Authentication Providers, then start the server again.
• On Business or Enterprise, the server never starts. Ask your admin to turn on the MCP servers in Copilot policy.
• With a key, it doesn't connect. Check VESSERO_API_KEY is set where VS Code starts, then restart VS Code.