Integrations · Model Context Protocol

HellouOne MCP server: connect Claude, ChatGPT and Cursor to your WhatsApp inbox

Yes, HellouOne has an MCP server. It runs at mcp.hellou.ai, any MCP client can connect with a sign-in or a personal token, and the assistant works with your conversations, contacts, inboxes, AI agents, reports and settings using exactly your permissions.

Read the MCP docs →Create account

What it is

What is the HellouOne MCP server?

The Model Context Protocol (MCP) is the open standard AI assistants use to call tools in other products. HellouOne runs a remote MCP server, so instead of copying chats into an assistant, the assistant connects to your account and acts there, as the administrator who connected it.

One URL for every account: https://mcp.hellou.ai/mcp (Streamable HTTP). The credential decides which account it sees.
Works with Claude (claude.ai, Claude Code, Claude Desktop), ChatGPT, Cursor and any other MCP client.
Sign in with OAuth 2.1 from hosted assistants, or use a personal hcm_ token from the CLI and desktop clients.
Reading is the default. Changes are opt-in per account and per token, and every change lands in the audit log.

Tools

What can an assistant do in your account?

The server lists every tool the connection may use, marks which ones only read and which ones change data, and returns customer text as data that the assistant must never follow as instructions.

Conversations

Read + change

Read WhatsApp, web chat and other channel conversations, filter them, reply, assign, label, close and reopen.

Contacts

Read + change

Search and read contacts and their attributes; create, update and label them.

Inboxes and teams

Read + change

See inboxes, agents and teams, membership and assignment settings; add or remove members.

AI agents and knowledge

Read + change

List the AI agents, their knowledge-base documents and guides; add documents and re-ingest them.

Campaigns, templates and Flows

Read + change

List WhatsApp templates and Flows, preview an audience and its cost, create, pause or cancel campaigns.

Reports

Read

Agent, team, conversation, sentiment and call reports, plus live conversation metrics and the account summary.

Automation

Read + change

Canned responses, macros, labels, custom attributes and automation rules.

Facebook marketing

Read + change

Ad accounts, lead forms and Facebook leads with their campaign insights.

Settings

Read + change

Business profile, working hours, widget appearance and each inbox's settings.

Setup

How do you connect an assistant?

Three ways, depending on the client. The full reference, including the prompt that lets the assistant set itself up, is in the docs.

1Sign in

claude.ai, ChatGPT or Cursor: add the URL and sign in

Add https://mcp.hellou.ai/mcp as a custom connector named HellouOne. The assistant discovers the sign-in on its own, opens the HellouOne consent page, and an administrator picks the account and decides whether the assistant may make changes. No token is pasted anywhere.

{
  "mcpServers": {
    "hellouone": { "url": "https://mcp.hellou.ai/mcp" }
  }
}

2Token

Claude Code and other CLIs: one command with a personal token

An administrator creates a token in Settings → Integrations → AI clients (MCP), names it after the client, picks an expiry and optionally allows changes. The token starts with hcm_ and is shown once.

claude mcp add --transport http hellouone https://mcp.hellou.ai/mcp \
  --header "Authorization: Bearer hcm_..."

3Ask

Or paste the setup prompt and let the agent do it

The docs page and the AI clients screen both carry a ready-made prompt. Paste it into Claude Code, Cursor, claude.ai or ChatGPT and the agent connects itself, lists its tools grouped by area and says which ones change data.

Keep tokens out of chat, logs and files other than your MCP config. Connected apps are listed, and can be disconnected, in Settings → Integrations → AI clients (MCP).

Read the MCP docs →

Control

Who controls what the assistant can do?

The server was built so that connecting an assistant never widens anyone's access.

The assistant acts as the administrator who connected it, with that person's permissions, nothing more.
Tools that change data are offered only when the account has Allow changes on and the token or sign-in was granted change rights.
Every tool that changes data is annotated as such, so well-behaved assistants ask before running it. Each change is written to the account's audit log.
OAuth 2.1 with PKCE, dynamic client registration and one-hour access tokens that refresh with rotation. Tokens are issued for the MCP endpoint only.
Customer text arrives inside <account_data> tags: it is data written by customers and agents, never instructions for the assistant.
Rate limit of 120 requests per minute per token; a token from someone who is no longer an administrator stops working.

FAQ

Questions about the MCP server

Does HellouOne have an MCP server?

Yes. HellouOne runs a public, remote MCP server at https://mcp.hellou.ai/mcp. Claude, ChatGPT, Cursor and any other MCP client can connect to it and work with a HellouOne account's conversations, contacts, inboxes, AI agents, campaigns, reports and settings.

Which AI assistants can connect?

Any client that speaks MCP over Streamable HTTP: claude.ai and ChatGPT (as a custom connector with sign-in), Cursor, Claude Code, Claude Desktop through a remote-server bridge, and your own agents built on the MCP SDKs.

Can an assistant send WhatsApp messages through MCP?

Yes, when the account allows changes and the token or sign-in was granted change rights. Replying inside an open conversation, assigning it or labelling it are change tools; the assistant sees them marked as such and should confirm with you before running them. Outside the 24-hour window WhatsApp only allows approved templates, which the campaign tools use.

Which plan includes the MCP server?

The public API, SDK and webhooks are available from the Starter plan. An administrator switches AI clients on in Settings → Integrations; if your account does not show the option, write to us from the app.

Is this the same as Meta's WhatsApp MCP server?

No. Meta's server helps a coding agent create a WhatsApp Business account and register a number on the Cloud API. HellouOne's server gives an assistant access to the day-to-day work of an account that already runs on HellouOne: the conversations, the contacts, the team and the reports.

What is the difference between MCP and the REST API?

The REST API and webhooks are for software you write and run yourself. MCP is for assistants a person is talking to: the assistant discovers the tools, decides which to call and asks before changing anything. Both are documented at one.hellou.ai/docs.