How to Connect Claude Code to MewCP
Add MewCP to Claude Code once, and Claude can use every app you have connected in MewCP: Gmail, Calendar, Slack, GitHub and the rest. Claude Code connects to MewCP directly over HTTP, so there is nothing to install.
There are two ways to set it up:
| Method | MewCP loads in | Best for |
|---|---|---|
| One command | Every project on your machine | Most people |
.mcp.json file | One project, for everyone who opens it | Sharing the setup with a team |
Before you start
- Claude Code installed. Check with
claude --version, or see Claude Code setup - A API Key from Dashboard → API Keys, see API Key
- At least one app connected in the dashboard under Servers
Option A: One command
Run this in your terminal, replacing API_KEY with your key:
Code
Claude Code prints an Added ... line when it has saved the server.
Keep --scope user. Without it, Claude Code uses its default local scope and MewCP loads only in the folder you ran the command from.
This is the entire configuration. One entry reaches every app you have connected, and connecting another app later needs no change here.
Option B: .mcp.json in a project
Use this to share MewCP with everyone who works in a repository. Each person still uses their own key, so each of them reaches their own apps.
-
Add the file
Create
.mcp.jsonin the project root, or add themewcpentry to the one you have:CodeKeep
"type": "http". Claude Code reads an entry without atypeas a local command and skips it.${MEWCP_API_KEY}is read from each person's environment, so the key never goes into version control. You can commit this file. -
Set your key
Add your key to your shell profile (
~/.zshrcor~/.bashrc), then open a new terminal:Code -
Approve the server
Run
claudein the project. Claude Code asks before it uses a server from a project's.mcp.jsonfor the first time. Approvemewcp.
Check it works
Run:
Code
mewcp should show ✔ Connected. Inside a Claude Code session, /mcp shows the same status and lets you see MewCP's tools.
You will see four tools, not the tools of every app: search, get_schema, list_accounts and call_tool. That is expected. Claude uses them to find and run the right tool for whatever you ask. See How MewCP works.
Then ask for something from an app you have connected:
Code
If you have two accounts connected for the same app, say which one you mean:
Code
Troubleshooting
MewCP works in one project but not in others
It was added with the default local scope, which belongs to the folder you ran the command in. Remove it there and add it again for all projects:
Code
claude mcp list shows ✘ Failed to connect
Usually MewCP rejected the key.
- Check the header reads
Authorization: Bearerfollowed by the whole key, which starts withmcp_live_. - With
.mcp.json, checkMEWCP_API_KEYis set in the terminal you start Claude from:echo $MEWCP_API_KEY. If it is not set, Claude Code sends the literal text${MEWCP_API_KEY}andclaude mcp listwarns about a missing variable. - A
403that says the billing period is not active means your MewCP plan needs renewing in the dashboard.
Claude Code does not retry an authentication error on its own. After fixing the key, start a new session, or open /mcp and reconnect mewcp.
The key is set but MewCP still gets no key
Claude Code never puts some credential variables into a remote server's headers, such as ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN and NPM_TOKEN. They read as empty, so MewCP receives Bearer with no key. Use a variable with a name of your own, such as MEWCP_API_KEY, as in the example above.
has a "url" but no "type"
The .mcp.json entry is missing "type": "http". Add it next to url.
⏸ Pending approval
The server comes from a project's .mcp.json and you have not approved it yet. Run claude in the project and approve it. To see the approval prompt again after declining, run claude mcp reset-project-choices.
Last checked against Claude Code's documentation on 13 October 2026.