Copy page

Connect AI Apps

How to Connect Cursor to MewCP

Add MewCP to Cursor once, and Cursor's Agent can use every app you have connected in MewCP: Gmail, Calendar, Slack, GitHub and the rest. Cursor connects to MewCP directly over HTTP, so there is nothing to install. The same setup works in the Cursor CLI.

---

Before you start

• Cursor installed and updated (download)
• A API Key from Dashboard → API Keys, see API Key
• At least one app connected in the dashboard under Servers

---

Set up MewCP

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

Keep the key out of a shared file

For a project's .cursor/mcp.json that goes into git, read the key from each person's environment instead:

Code
"headers": {
  "Authorization": "Bearer ${env:MEWCP_API_KEY}"
}

Each person sets MEWCP_API_KEY in their shell profile, such as ~/.zshrc, then restarts Cursor. Each of them reaches their own apps with their own key.

Cursor writes environment variables as ${env:NAME}. A plain ${MEWCP_API_KEY}, as used in Claude Code, is not read by Cursor.

---

Check it works

Open Customize in Cursor's sidebar and go to MCPs. MewCP should be listed and switched on.

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

Then ask the Agent for something from an app you have connected:

Code
What is on my calendar tomorrow?

Cursor asks for approval before each MCP tool call by default. Click the arrow next to the tool name to see what it is about to send.

In the Cursor CLI, run agent mcp list to see MewCP's status and agent mcp list-tools mewcp to see its tools.

---

Troubleshooting

MewCP is not listed, or shows an error

Open the Output panel with Cmd+Shift+U on macOS or Ctrl+Shift+U on Windows and Linux, and choose MCP Logs from the dropdown. It shows connection and authentication errors for each server.

• Check mcp.json is valid JSON. A missing comma, or a trailing comma after the last entry, stops the file from loading.
• Check the file is in the right place: ~/.cursor/mcp.json, or .cursor/mcp.json inside the project folder, not the project root.

The log shows 401 or 403

MewCP rejected the key.

• Check the header reads Bearer followed by the whole key, which starts with mcp_live_.
• If you use ${env:MEWCP_API_KEY}, Cursor must be able to see the variable. Cursor started from the Dock or Start menu may not have it. Set it in your shell profile and restart Cursor completely.
• A 403 that says the billing period is not active means your MewCP plan needs renewing in the dashboard.

Changes to mcp.json do nothing

Restart Cursor. If MewCP is defined in both the project's .cursor/mcp.json and your global ~/.cursor/mcp.json, the project's entry wins, so edit that one.

MewCP is blocked on a Cursor Enterprise team

Enterprise admins can limit which MCP servers members may run with an MCP allowlist. Ask your admin to add a URL entry for https://gateway.mewcp.com under Team Settings → MCP Configuration.

---

Last checked against Cursor's documentation on 13 October 2026.