Copy page

Connect AI Apps

How to Connect VS Code to MewCP

Add MewCP to VS Code once, and GitHub Copilot Chat can use every app you have connected in MewCP: Gmail, Calendar, Slack, GitHub and the rest. VS Code connects to MewCP directly over HTTP, so there is nothing to install.

There are two ways to set it up:

Method	Where the key lives	Best for
Copilot config file	In the file	Most people. Also works in GitHub Copilot CLI
Prompt for the key	Stored securely by VS Code, not in the file	Keeping the key out of config files

---

Before you start

• VS Code with GitHub Copilot set up (Copilot in VS Code)
• A API Key from Dashboard → API Keys, see API Key
• At least one app connected in the dashboard under Servers

---

Option A: Copilot config file

To share MewCP with everyone who works in a repository, put the same JSON in a .mcp.json file at the workspace root instead. Leave your key out of a file you commit: use Option B for that workspace, or have each person keep their own key in their user file.

---

Option B: Prompt for the key

VS Code can ask for your key once and store it securely, so the key never sits in a config file.

VS Code does not pass servers that prompt for input to Agent Host sessions. If MewCP is missing there, use Option A.

This is the entire configuration either way. One entry reaches every app you have connected, and connecting another app later needs no change here.

---

Check it works

Run MCP: List Servers from the Command Palette. MewCP should be listed as running. In the Chat view, select Configure Tools in the chat input to see its tools.

You will see four tools, not the tools of every app: search, get_schema, list_accounts and call_tool. That is expected. Copilot uses them to find and run the right tool for whatever you ask. See How MewCP works.

Then ask Copilot in agent mode for something from an app you have connected:

Code
What is on my calendar tomorrow?

VS Code may ask you to confirm each tool call.

---

Troubleshooting

Chat shows an error for MewCP

Run MCP: List Servers, select mewcp, and choose Show Output. The output shows why it failed to start or connect. You can also select the error in the Chat view and choose Show Output.

MewCP does not appear at all

Check the top-level key matches the file:

File	Top-level key
~/.copilot/mcp-config.json or .mcp.json	mcpServers
User profile mcp.json or .vscode/mcp.json	servers

Older guides put MCP servers in settings.json under "mcp". Move the entry into one of the files above.

The output shows 401 or 403

MewCP rejected the key.

• Check the header reads Bearer followed by the whole key, which starts with mcp_live_.
• With Option B, enter the key alone when VS Code asks. The config already adds Bearer .
• A 403 that says the billing period is not active means your MewCP plan needs renewing in the dashboard.

MewCP was not started because you declined the trust prompt

Run MCP: Reset Trust from the Command Palette, then send a chat message again and confirm.

MCP tools are turned off by your organization

On Copilot Business and Enterprise plans, an admin controls whether MCP servers can be used in Copilot. If no MCP server works, ask your admin to allow MCP servers, or to add https://gateway.mewcp.com to your organization's allowlist. See GitHub's MCP allowlist guide.

---

Last checked against VS Code's documentation on 13 October 2026.