Skip to main content
Use this remote MCP URL: 
https://api.whatsapp-use.com/mcp/whatsapp

​
Generic setup

Use these values in any client that supports remote HTTP MCP servers:
SettingValue
Namewhatsapp-use
TransportHTTP or Streamable HTTP
URLhttps://api.whatsapp-use.com/mcp/whatsapp
AuthenticationOAuth
If your client uses JSON configuration, the server entry usually looks like this: 
{
  "mcpServers": {
    "whatsapp-use": {
      "type": "http",
      "url": "https://api.whatsapp-use.com/mcp/whatsapp"
    }
  }
}
MCP clients use different config file locations and command names. The URL, transport, and OAuth behavior are the stable parts.

​
Optional client commands

These are optional shortcuts. The generic URL and JSON config above are the source of truth. 
claude mcp add --transport http --scope user whatsapp-use https://api.whatsapp-use.com/mcp/whatsapp
Your client opens a browser when OAuth authorization is required.

​
Install flow

1

Add the remote MCP server

Add the WhatsApp Use URL to your MCP client with HTTP transport.
2

Complete OAuth

Your MCP client opens a browser. Sign in, choose your organization, and authorize the client.
3

Pair WhatsApp first if needed

If your organization has no connection, create an API key and pair WhatsApp from the platform dashboard before authorizing MCP.
4

Use tools

After authorization, your MCP client can call WhatsApp tools for the selected connection.

​
QR pairing

The install command only adds the MCP server to your client. Pairing happens in the platform dashboard because it requires account access, organization selection, and a WhatsApp QR scan. If you already have a paired connection, OAuth can authorize the MCP client immediately. If you do not, create an API key, pair WhatsApp in the dashboard, then retry MCP authorization.