Hello MCP server
Provides tools for interacting with the WhatsApp Business API via Hello, including listing sending numbers, sending messages and templates, checking delivery status, uploading media, managing templates, and configuring webhook overrides.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Hello MCP server for the WhatsApp Business API
Connect Claude, Cursor, Codex and other AI assistants to Hello, the WhatsApp Business API. Ask the assistant to list your numbers, send messages and templates, check delivery and manage templates.
This package is a small stdio MCP server for clients that cannot talk to a remote server
(Claude Desktop, some IDEs). It does not implement any tools itself: it forwards everything to the
hosted Hello MCP endpoint (https://helloapi.lakshyapocketlab.com/mcp), so the tools are always the
ones the backend serves today.
Node.js 18 or newer
One runtime dependency: the official
@modelcontextprotocol/sdkYour API key is sent only as a Bearer token to the Hello endpoint. It is never logged.
Quick start
Two steps for every client:
Get an API key. Create one (
hello_live_…) in the Hello dashboard under Integrations.Add the server to your client, using the snippet for it below.
Claude Code connects to the hosted endpoint directly, which is the recommended setup. Clients that only speak stdio use this npm package instead.
Claude Code (recommended: remote HTTP)
claude mcp add --transport http hello https://helloapi.lakshyapocketlab.com/mcp \
--header "Authorization: Bearer hello_live_…"Run claude mcp list to confirm the server is connected.
Claude Desktop (npx)
Edit claude_desktop_config.json (Settings, Developer, Edit Config):
{
"mcpServers": {
"hello": {
"command": "npx",
"args": ["-y", "@lakshyapocketlab/hello-mcp"],
"env": { "HELLO_API_KEY": "hello_live_…" }
}
}
}Restart Claude Desktop. The Hello tools appear in the tools menu.
Cursor (npx)
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (all projects):
{
"mcpServers": {
"hello": {
"command": "npx",
"args": ["-y", "@lakshyapocketlab/hello-mcp"],
"env": { "HELLO_API_KEY": "hello_live_…" }
}
}
}Codex (npx)
Add to ~/.codex/config.toml:
[mcp_servers.hello]
command = "npx"
args = ["-y", "@lakshyapocketlab/hello-mcp"]
env = { HELLO_API_KEY = "hello_live_…" }Codex can also use the hosted endpoint directly: set url = "https://helloapi.lakshyapocketlab.com/mcp" and bearer_token_env_var = "HELLO_API_KEY".
Related MCP server: whatsapp-mcp-server
Setup
Requirements
Node.js 18 or newer, for
npxor a global install.A Hello API key. The server reads it from
HELLO_API_KEYin its environment and sends it only as a Bearer token to the Hello endpoint.
Configuration
Setting | Default | Description |
| required | Your Hello API key. The server exits with an error on stderr if it is missing. |
|
| MCP endpoint to proxy to. |
| Same as | |
| Print usage or the version and exit. |
To point the server at another endpoint, such as a local or staging deployment, set HELLO_MCP_URL in the client's env block, or pass --url:
HELLO_API_KEY=hello_live_… npx @lakshyapocketlab/hello-mcp --url http://localhost:8080/mcpLogs go to stderr only, because stdout carries the MCP stream.
Tools
The server exposes the tools of the hosted endpoint, so the list is always the one the backend serves. These are the tools it provides today.
Tool | What it does |
| Checks that the API key works. |
| Lists the sending numbers with their |
| Sends a WhatsApp message in Cloud API format (text, template, media, interactive, reaction, ...), or marks a received message as read. Real and billed. |
| Gets a sent message by its ID: queued, sent, delivered, read or failed. |
| Uploads a file (about 7 MB) for a media message or template header, and returns a media ID. |
| Lists a WhatsApp Business Account's templates, filtered by status, category or language. Paged. |
| Gets one template with its components and |
| Submits a new template to Meta for review. |
| Creates or edits up to 100 templates in one call. |
| Edits an approved, rejected or paused template. It goes back to review. |
| Re-reads every template of the account from Meta. |
| Permanently deletes one language of a template. Destructive. |
| Permanently deletes every language of a template name. Destructive. |
| Shows whether a number's webhook is overridden to the user's own URL, and that override's status. |
| Points a number's webhook at the user's own URL. Hello stops showing that number's incoming messages and statuses. |
| Removes the direct webhook, so Hello receives the number's events again. |
| Applies a stored direct webhook on Meta again, when its status is |
The server also provides get_guide, with reference topics messages (message formats), templates, errors (error codes and fixes) and direct_webhook.
Messages are real and billed, and the delete tools are permanent. Free-form messages need an open 24-hour window with the recipient; otherwise the assistant should send an approved template. set_webhook_override changes where a number's events go, so the assistant should confirm it with you first.
Troubleshooting
Symptom | Fix |
| Add the key to the server's |
| Check |
| The server accepts only |
| Check your network, proxy or firewall, and that the URL is reachable from this machine. |
Authentication errors from a tool | The key is wrong or has been revoked. Create a new key in the dashboard and update the client's configuration. |
Tools do not appear in Claude Desktop | Check that the JSON is valid, then quit Claude Desktop completely and reopen it. |
| Check the Node version with |
A send fails with error code | The recipient has not messaged the number in the last 24 hours. Send an approved template instead. |
If none of these apply, contact support@lakshyapocketlab.com and include the FBTrace ID from the error, if one is shown.
How it works
MCP client ──stdio──▶ hello-mcp ──Streamable HTTP + Bearer key──▶ https://helloapi.lakshyapocketlab.com/mcpinitialize, tools/list and tools/call (plus prompts and resources if the remote advertises them) are forwarded unchanged, and errors from the remote reach your client as-is. Nothing is reimplemented locally, so the tool list and results never drift from the hosted endpoint.
Links
Docs: lakshyapocketlab.com/docs, including the MCP integration guide
SDKs: hello-node, hello-python, hello-go
Examples: hello-examples
Support: support@lakshyapocketlab.com
License
MIT, Copyright Lakshya Pocket Lab.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Send WhatsApp messages and templates, manage chats, contacts, broadcasts and AI agents.
WhatsApp for AI agents — your own number or the official Cloud API: messages, media, templates.
Run WhatsApp Business campaigns from any AI assistant: contacts, segments, and broadcasts.
Read, summarize and send your own WhatsApp messages from AI assistants (OAuth 2.1).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send WhatsApp messages, templates, and retrieve media through the WhatsApp Cloud API. Provides webhook handling and seamless integration with Meta's WhatsApp Business platform.23ISC
- AlicenseAqualityDmaintenanceConnects AI assistants to the official Meta WhatsApp Cloud API for managing conversations and sending various message types through natural language. It provides tools for media management, template messages, and real-time webhook processing without the risk of account bans.1827MIT

GoWA MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents and tools to send and manage WhatsApp messages, media, statuses, and scheduled sends across multiple linked devices.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage WhatsApp instances, send messages and campaigns, handle incoming messages, webhooks, members, and metrics through 30 authenticated tools, with an optional WhatsApp-to-assistant bridge.Apache 2.0