MCP server

Point your AI assistant at the WhatsApp inbox.

MCP is the open protocol that gives an assistant real tools. Ours lets the client you already work in read a thread, draft the reply and queue the campaign.

Start free trial

7 days free · No credit card · Cancel anytime

How it fits

One protocol between the model and the message

Your assistant already knows how to call tools. What it lacks is a way into WhatsApp. The MCP server is that way in: it publishes a catalogue of WhatsApp actions, the model picks the ones the request needs, and every call lands on your number through the same account and permissions your agents work under.

Remote and hosted, so there is nothing to run on your laptop and nothing to keep patched.
Authenticated with an ordinary API key, scoped to one account.
Reads answer straight away; writes go through your client's approval prompt.
Whatever it sends appears in the shared inbox like any other message.

See the setup API documentation

MCP session3 tool calls

"Anything unanswered since Friday?"get_whatsapp_unread_chats

"Summarise the thread with the hotel"get_whatsapp_chat_messages

"Tell them the parts ship Tuesday"send_whatsapp_message

Two reads ran on their own. The third wrote to a customer, so it asked first.

Clients

Bring the assistant you already use

Nothing on this page is a one-off integration. Any client that can add a remote MCP server can work your WhatsApp inbox, and it keeps working when you switch to the next one.

Claude Desktop

Add the server once under connectors and every new conversation opens with the WhatsApp tools already loaded.

Desktop
Remote MCP

Claude Code

One command registers it in the CLI, so a terminal session can pull a thread or check a campaign between commits.

CLI
Terminal

Cursor

Drop the endpoint into the editor's MCP settings and ask for a customer's history without leaving the file you are in.

Editor
Agent mode

VS Code

Editor
Workspace config

ChatGPT

Where your account allows custom connectors, point one at the endpoint and the tools show up in the chat you already use.

Connector

Anything else that speaks MCP

Other editors, other desktop clients, an agent you wrote yourself. The protocol is public, so the server does not care what sits on the other end.

Custom agent
SDK

In practice

Say it in plain language

There is no syntax to memorise and no tool name to remember. You describe the outcome you want; the assistant works out which calls that takes and shows you the plan before it acts.

Triage

Which chats have gone quiet for more than a day?
Show me everything still unassigned this morning.
Who wrote in overnight, and what did they want?

Replies

Draft a warm, short answer to the builders.
Send the delivery window we agreed to the last chat.
Reply in Spanish and keep it under two lines.

Handover

Move every billing question to the finance department.
Leave an internal note explaining where this one stands.
Resolve the shipping threads that got their tracking link.

Campaigns

Queue Thursday's reminder to the list I imported last week.
What did September deliver, and how much of it was read and replied to?
Pause the campaign that is still running and tell me why.

Contacts

Label everyone who asked about trade pricing this month.
Find the contact I spoke to about the Bilbao order.
Check these forty numbers are on WhatsApp before I import them.

Reporting

How many first replies took over an hour yesterday?
Break last week down by department.
Export the supplier thread so I can attach it to the claim.

Setup

One URL, and that is the integration

The server is remote, so there is no package to install and no process to babysit. Copy the endpoint, put your API key on the end of it, restart the client.

Server endpointhttps://api.wali.chat/mcp?key=YOUR_API_KEY

Swap YOUR_API_KEY for a key from your account settings. It is the same credential the REST API uses, with the same permissions, so revoking it there cuts the assistant off on its next call.

Start free trial Open the API tester

# claude_desktop_config.json
{
  "mcpServers": {
    "walichat": {
      "type": "http",
      "url": "https://api.wali.chat/mcp?key=YOUR_API_KEY"
    }
  }
}

# one command, from any directory
claude mcp add --transport http walichat "https://api.wali.chat/mcp?key=YOUR_API_KEY"

# .cursor/mcp.json
{
  "mcpServers": {
    "walichat": {
      "url": "https://api.wali.chat/mcp?key=YOUR_API_KEY"
    }
  }
}

# .vscode/mcp.json
{
  "servers": {
    "walichat": {
      "type": "http",
      "url": "https://api.wali.chat/mcp?key=YOUR_API_KEY"
    }
  }
}

FIRST THING TO TRY

> Anything unread on WhatsApp?

~1 min
Create an API key
From the API keys panel in your account, using the same credential the REST API uses. One key per assistant keeps the trail readable.
~1 min
Paste the endpoint
Into your client's MCP settings, with the key on the end of the URL. That is the whole configuration.
live
Ask for something
Restart the client and the WhatsApp tools appear in its tool list. Start with a read so you can watch it work.

Toolbelt

The whole product, grouped six ways

The server exposes the working parts of WaliChat rather than a thin messaging slice of it. These are the tool names your client will list once it connects.

Messages

Send text, media and documents, pull the history of a thread, and act on what is already in it.

send_whatsapp_message
get_whatsapp_chat_messages
manage_whatsapp_message_interactions

Chats

List and search the inbox, filter by status, date or contact type, and surface what nobody has answered.

get_whatsapp_chats
get_whatsapp_unread_chats
search_whatsapp_chats_by_name
get_whatsapp_chats_by_status

Team & routing

Hand work to the right person, move a thread into a department, and check what is stacking up in the queue.

manage_whatsapp_team
manage_whatsapp_departments
manage_whatsapp_queue

Campaigns

Build the audience, schedule the send, and read back what happened recipient by recipient.

manage_whatsapp_campaigns
manage_whatsapp_campaign_contacts
list_whatsapp_templates

Contacts & labels

Label a conversation, group by segment, and confirm a number is reachable before you write to it.

manage_whatsapp_labels
verifyWhatsAppNumberExists
get_whatsapp_chats_by_contact_type

Files & reporting

Attach a file, find one that was sent months ago, and pull statistics or a full export of a thread.

upload_whatsapp_file_from_url
search_whatsapp_chat_files
get_whatsapp_chat_statistics
export_whatsapp_chats

Choosing

MCP server, or the REST API?

They reach the same account and the same numbers. The difference is who is driving, and whether anyone is watching while it happens.

The MCP server compared with the REST API and webhooks
Aspect	MCP server	REST API & webhooks
Who drives	A person, thinking out loud through an assistant.	Your code, on a schedule or an incoming event.
How you ask	Plain language, one request at a time.	An HTTP call per action, written once and reused.
Best for	Ad-hoc work like triage, drafting and digging through history.	Repeatable work like order updates, alerts and keeping a CRM in step.
Runs when	You are there to read what it proposes.	Unattended, day and night.
Approval	Your client puts a write in front of you first.	Whatever your own code decides.
Setup	Paste one URL into a settings panel.	Write the integration and host it somewhere.

Most teams run both, using an assistant for the work that needs judgement and the API for the work that repeats. See the developer side.

Control

What it can do, and what it cannot

Giving an assistant a live customer channel is a real decision. Four things make it a reversible one.

The key is the boundary

The server authenticates with an ordinary WaliChat API key. It reaches the account that key was issued for and nothing beyond it. Delete the key and the next call fails.

Writes ask first

Reading a chat is harmless and runs on its own. Sending, assigning or launching a campaign is a tool call, and any client that supports approval, Claude included, shows it to you before it goes anywhere.

One key per assistant

Issue a separate key for each place you connect the server. If you ever need to cut one off, you cut off one connection rather than the whole team.

It leaves a trail

Anything the assistant sends arrives in the shared inbox as a normal outbound message. Your team sees it in the thread, not weeks later in a log.

Questions, answered

What is MCP, in one paragraph?

MCP stands for Model Context Protocol. It is an open specification for describing tools to an AI assistant: what each one does, what it takes and what it gives back. A client that speaks it can pick up any MCP server and start working without a bespoke integration being built first. WaliChat runs one of those servers for WhatsApp.

Is there anything to build?

No. Connecting the server is a URL and an API key in your client's settings panel. Code only enters the picture if you are assembling your own agent, and even then the protocol handles the introductions.

Which assistants can I use it with?

Any client that supports remote MCP servers over HTTP. Claude Desktop and Claude Code do, as do Cursor, VS Code and several other editors, and ChatGPT where your account allows custom connectors. Because the standard is open, the list keeps widening without anything changing on our side.

Do I have to host or install anything?

No. The server is hosted and maintained for you; your client just points at a URL. There is no package to install, no port to open and no version to keep current.

What exactly does the key give it access to?

The server authenticates with a WaliChat API key passed on the endpoint URL, and it reaches the account that key belongs to and nothing else. Keys are issued and withdrawn from the API keys panel in your account, and withdrawing one takes effect on the very next call.

Can the assistant send messages without asking me?

That is decided by your client, not by the server. Clients with tool approval show you the call and wait for a yes. If you deliberately run an agent unattended, give it a key issued only for that job so its reach stays narrow.

Does it work with the number I already have connected?

Yes. The MCP server sits on the same API as the rest of WaliChat, so it works with the numbers and the team structure already in your account. Nothing has to be reconnected or migrated to switch it on.

How is this different from the REST API?

It is the same account seen from a different angle. The API is for software you write and leave running, while MCP is for a person working through an assistant. Most teams end up with both, and the API half is covered on the developers page.

Stop losing WhatsApp messages today

Join 5,000+ teams already using WaliChat to grow faster.

Start Free Trial NowSeven days on us · Nothing to pay up front · Connected in minutes

Point your AI assistant at the WhatsApp inbox.

One protocol between the model and the message

Bring the assistant you already use

Claude Desktop

Claude Code

Cursor

VS Code

ChatGPT

Anything else that speaks MCP

Say it in plain language

Triage

Replies

Handover

Campaigns

Contacts

Reporting

One URL, and that is the integration

Create an API key

Paste the endpoint

Ask for something

The whole product, grouped six ways

Messages

Chats

Team & routing

Campaigns

Contacts & labels

Files & reporting

MCP server, or the REST API?

What it can do, and what it cannot

The key is the boundary

Writes ask first

One key per assistant

It leaves a trail

Questions, answered

Stop losing WhatsApp messages today