WhatsApp MCP in Zed: Add Blueticks as a Remote Server With One URL

Short answer: in Zed, open Settings → AI → MCP Servers, add a remote server, and give it the URL https://api.blueticks.co/mcp. Zed then asks you to sign in to Blueticks through the standard MCP login. Once approved, the Zed agent has WhatsApp tools for reading chats and sending messages from your own number.

This page is the setup only. For what a coding agent can do with it, see Cursor on WhatsApp and Claude Code on WhatsApp. The idea is the same; only the config differs.

Can you connect Zed to WhatsApp?

Yes, through MCP. Per the Zed docs, MCP servers are configured under the context_servers key of your settings file, and a server is either local (a command with optional args and env) or remote (a url with optional headers). A remote server with only a url and no Authorization header makes Zed prompt you to sign in through the standard MCP OAuth flow.

Blueticks runs a hosted MCP endpoint at https://api.blueticks.co/mcp that signs in this way. You need a Blueticks account with a WhatsApp number connected.

How do you set it up? Four steps

1. Open the MCP settings. Go to Settings → AI → MCP Servers, or run the agent: open settings action and pick MCP Servers.
2. Add the server. Click Add Server, choose Add Remote Server, and enter the URL. Or run zed: open settings file and add this:

"context_servers": {
  "blueticks": {
    "url": "https://api.blueticks.co/mcp"
  }
}

3. Sign in. Zed prompts you to authenticate. Log in to Blueticks and approve access. When the indicator dot next to the server in Settings → AI → MCP Servers is green with the tooltip "Server is active", it is running.
4. Check it. Ask the agent: "Using Blueticks, list my five most recent WhatsApp chats." It should call a Blueticks tool and answer from your account.

What if you prefer a key instead of a login?

Blueticks also ships @blueticks/mcp, an npm package that runs as a local server and reads a bt_live_ key from the BLUETICKS_API_KEY environment variable. In Zed's local-server shape that is:

"context_servers": {
  "blueticks": {
    "command": "npx",
    "args": ["-y", "@blueticks/mcp"],
    "env": { "BLUETICKS_API_KEY": "bt_live_your_key_here" }
  }
}

Create the key on the Blueticks API page; Blueticks shows it once. The package and key are documented in the MCP docs and the authentication docs.

Does Zed ask before the agent sends a message?

By default, yes. Per the Zed docs, the default for tool actions is "confirm", which prompts before any tool action, including MCP tool calls. In Zed v0.224.0 and later this is the agent.tool_permissions.default setting. Leave it on confirm for Blueticks: everything the agent sends goes out from your own WhatsApp number, so read the draft before you approve a send.

Which tools does the agent get?

The exact set depends on the connection and the package version, so ask the agent to list the Blueticks tools it can see. Reading chats and sending messages are the two it uses most.

How do you keep access safe?

With the login route there is no key to store. If you use a key, treat it as a password and do not commit it to source control. A settings file you keep in a dotfiles repo is easy to publish by accident, so prefer the login route there. To rotate a key, create a new one, switch over, then revoke the old one in the dashboard.

FAQ

Is there a free plan?

The API and the hosted connector allow 5 requests per 6 hours on the free plan, shared between them. Paid plans have no request limit. See the pricing page.

Where do I get help?

Start with the hosted WhatsApp MCP page and the MCP docs.