Cosend

npx add-mcp 'https://mcp.cosend.app/mcp'

MCP server

How to connect an MCP client to your WhatsApp number: the endpoint, OAuth sign-in, setup for Claude Code, Claude Desktop and other clients, and the scopes.

Cosend runs a remote MCP server at https://mcp.cosend.app/mcp over Streamable HTTP. It exposes your WhatsApp number as tools that any MCP-capable agent can call. For the full list of tools, see MCP.

Endpoint

https://mcp.cosend.app/mcp

The server keeps no session state, so it needs no session header or handshake. It is an OAuth 2.1 resource server: your MCP client signs you in the first time it connects.

Claude Code

claude mcp add --transport http cosend https://mcp.cosend.app/mcp

Then run /mcp in Claude Code to complete the OAuth sign-in. claude mcp list shows the server as needing authentication while the sign-in is pending.

To install the server for yourself only, or for one project:

claude mcp add --transport http cosend https://mcp.cosend.app/mcp --scope user
claude mcp add --transport http cosend https://mcp.cosend.app/mcp --scope project

To share the configuration with your team, commit it in .mcp.json:

{
  "mcpServers": {
    "cosend": {
      "type": "http",
      "url": "https://mcp.cosend.app/mcp"
    }
  }
}

Claude Desktop and claude.ai

Go to Settings → Connectors → Add custom connector and paste the URL. Your browser opens the OAuth sign-in.

On a Claude Team or Enterprise plan, an owner adds the connector for the whole team before members can enable it. Leave the advanced settings empty: Cosend supports Client ID Metadata Documents and dynamic client registration, so the client registers itself. The advanced settings are for teams that register clients in advance.

Other clients

Any MCP client that supports Streamable HTTP with OAuth connects to the same URL.

{
  "mcpServers": {
    "cosend": { "type": "streamable-http", "url": "https://mcp.cosend.app/mcp" }
  }
}

Scopes on the consent screen

The consent screen offers 22 scopes, and what you approve is exactly what the API enforces. They are workspace API key scopes, plus the two campaign scopes, which only people and AI apps hold.

Scope	Grants	Risk
messages:read	Conversations and messages	Low
messages:write	Sending WhatsApp messages	High: messages go to your customers
contacts:read	Contacts and their details	Low
contacts:write	Creating and updating contacts, tags and consent	Medium
templates:read	Templates and their review status	Low
templates:write	Drafting templates and submitting them to Meta	Medium: templates affect your quality rating
automations:read	Automations, versions and validation reports	Low
automations:write	Creating, updating, deploying and enabling automations	High: automations send messages to your customers
runs:read	Run history and step-by-step records	Low
runs:write	Starting and canceling runs	Medium
connectors:read / connectors:write	Connected accounts in other services	Medium: data in other services
usage:read	Usage and billing totals	Low
members:read	The workspace’s members and their roles	Low
billing:read	Your plan and billing details	Low
settings:read	The workspace’s data policy and setup progress	Low
connections:read	Your WhatsApp numbers, their settings and business profiles	Low
connections:write	Changing a number’s settings, display name and business profile, each after you approve its preview, and refreshing a number’s state from Meta	Medium: customers see the business profile
approvals:read	The actions waiting for a person’s decision	Low
approvals:write	Holding an action for a person’s decision	Low
campaigns:read	WhatsApp campaigns and what each one sent	Low
campaigns:write	Setting up campaigns for your saved audiences and stopping them; each send or schedule waits for your approval of its preview	High: campaigns message many customers

Every scope is selected when the consent screen opens. Keep only the ones the agent needs.

Your AI app acts with your own role in the workspace. The scopes that change automations, integrations and numbers, and the billing and campaign scopes, go to owners and admins.

Campaigns are on Starter and above. An AI app lists your saved audiences and campaigns, sets up and changes drafts, previews a campaign, and sends or schedules it once you approve that preview. Connected Cosend before campaigns arrived? Remove Cosend in your AI app and add it again to switch on the campaign tools.

Connected AI apps

Settings › Connected AI apps in the dashboard lists the AI apps connected to your workspace, who connected each, what it may do and when it was last used. Owners and admins see every app, and a member sees the ones they connected. Remove ends an app’s access at once. AI platforms that need a registered client sign in with one Cosend registers for them, on the same consent screen.

Blocked customers

An AI app cannot send to a customer who is blocked on a number. Block in Cosend is per number and separate from blocking in WhatsApp itself, which Meta manages.

Scopes reserved for people and API keys

These scopes are granted to people and API keys only, so an agent holds only what you approve. Connecting or disconnecting a WhatsApp number is a person’s step too, through Meta’s Embedded Signup: the agent can give you a setup link for it.

Scope	Reason
keys:write	API keys are created in the dashboard, so every key stays visible, revocable and audited
runtime:proxy	The Runtime API accepts connection keys only, because each Graph request names its WhatsApp number in the path and a connection key fixes that number
Wildcard scopes	Each scope covers one area, as the MCP specification’s security guidance recommends

Notifications and webhook endpoints are managed through the REST API and the dashboard, so their scopes live there rather than on the consent screen.

Plans

The MCP server is included on every plan, including Free. Messages, automation runs and AI conversations sent through the MCP server count toward your plan’s allowances. See pricing.