MCP server

Give your AI agent WhatsApp

A hosted MCP server with 36 tools. Once you sign in with your account or a key, the agent reads the conversation, replies, reacts and looks up contacts on your number, limited to what you allowed.

Create a free account

Read the MCP server guide

WhatsApp support run by an AI agent

CustomerHi! Can I move my appointment to Friday?

list_messagesreads the conversation to understand the request
send_typing_indicatorshows "typing" while it prepares the answer
send_textanswers the customer with a normal message

AgentSure! I moved it to Friday at 10 AM. See you then!

Illustrative example. Each step is one MCP server tool called by the agent.

Connect your MCP client

The server is at https://mcp.turbonotify.com. If your client supports sign-in, paste the address and sign in with your account. If it doesn't, or if the agent runs on its own, send your key in the Authorization header of every request.

Claude Code (terminal): after the command, run /mcp and sign in with your account

claude mcp add --transport http turbo-notify \
  https://mcp.turbonotify.com

With a key: Cursor and Claude Code (.mcp.json)

{
  "mcpServers": {
    "turbo-notify": {
      "type": "http",
      "url": "https://mcp.turbonotify.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop: Add it as a custom connector: paste the server address and sign in with your account, or enter your key as a request header. The guide walks you through it.
Agent frameworks: Agno, CrewAI, LangGraph and other MCP clients: set the server address, the Streamable HTTP transport and the authorization header.

Without writing code

If you build automations in n8n, connect the workflow's agent to WhatsApp through the MCP client node.

1In a workflow with the AI Agent node, add the MCP Client Tool.
2In Endpoint, enter https://mcp.turbonotify.com and choose the HTTP Streamable transport.
3In Authentication, choose Bearer Auth and create a credential with your key (YOUR_API_KEY) as the token.
4Ask the agent to list your numbers: if it answers, the connection works.
5To have the agent answer whoever messages your number, start the workflow with a Webhook node and register its URL in the dashboard (paid plans).

Other automation tools work the same way when they accept a remote MCP server with an authorization header. Claude's custom connector accepts the address and your account; for other hosted assistants, use the key in the header.

What the agent can do

36 tools covering the API's operations, limited to what you allowed the agent.

Send: Text, media, location, contact card, calendar event and link button.
Reply and act: Reply with a quote, react, edit, delete, show "typing" and mark as read.
Read messages: List conversations, read a message and see its status, receipts and reactions.
Contacts: List and look up contacts, see the profile picture and refresh a contact's details.
Groups: List and look up groups and see the group picture.
Numbers, usage and events: See the account's numbers, reconnect or disconnect a number, check quotas, usage and events.

No tool creates, renames or removes numbers, or changes billing or keys. Those operations stay in the dashboard or the API.

Some tools depend on the plan: reacting and showing "typing" start on Lone Wolf; marking as read, seeing read receipts and sending to groups start on Business. See what each plan includes in Plans and pricing.

You control what the agent does

The agent acts on behalf of your account, with the access you gave it.

Grant only the permissions it needs
When you sign in with your account, choose the permissions on the approval screen and disconnect the app in Connected apps when you no longer need it. With a key, the scopes are fixed when you create it: make one just for the agent. An agent that only replies does not need to reconnect numbers.
Treat incoming messages as third-party text
A message may try to give the agent orders. Never let a conversation change the agent's instructions, and ask a person to confirm sensitive actions.
No tool creates a charge
Reconnecting and disconnecting a number cost nothing. Creating, removing and pairing numbers stays in the dashboard or the API, out of the agent's reach.
Plan limits apply to the agent
Sending pace and per-number quotas apply the same way: the agent never sends faster than your account.

See the support agent example on GitHub