WhatsApp MCP
lharriesLABSCO SUMMARY
Spec-generated, and from the vendor.
Generating from the OpenAPI document means the tool set does not drift behind the API, and the pinnable spec path lets you freeze it deliberately when you would rather not have the surface change under you. It comes from YCloud themselves, so the account, the key and the endpoint are all first-party — messaging is billed to that account.
What it is
The YCloud team's MCP server for their WhatsApp Business API. Rather than hand-writing a tool per endpoint, it reads YCloud's published OpenAPI specification and generates the tool set from it, handling parameter types and validation automatically — so the surface tracks the API rather than the repository's release schedule.
What you get
- Tools generated automatically from the YCloud WhatsApp OpenAPI specification, covering the platform's endpoints without per-endpoint configuration
- Parameter types and validation derived from the spec, so a malformed call fails before it reaches the API
- Authentication carried on every request as the
X-API-Keyheader - The specification source itself overridable through
OPENAPI_SPEC_PATH, which defaults tohttps://docs.ycloud.com/openapi.json— you can pin a local copy instead of fetching the live one
Requirements
A YCloud account and its API key, found in the console under the developer page. The key goes in API_HEADERS in the form X-API-Key:your-api-key-here; API_BASE_URL defaults to https://api.ycloud.com/v2. Node.js v16.0.0 or higher and npm v7.0.0 or higher; clone, npm install, npm run build, then point your client at build/index.js.
Setup effort
Build from source — git clone https://github.com/YCloud-Developers/ycloud-whatsapp-mcp-server.git
USE CASES
01
Reaching WhatsApp Business operations from an assistant
Add the server with your key and the generated tools cover the platform's endpoints without you mapping each one.
02
Checking account state before sending anything
Ask the assistant a plain question about your YCloud account and let it pick the endpoint, as the README's own balance example does.
03
Keeping the tool surface stable
Point the spec path at a local copy so the tools do not change when YCloud publishes a new version of the document.
BEFORE YOU INSTALL
What to know first
Requires
- Node.js v16.0.0 or higher
- npm v7.0.0 or higher
- A YCloud account and API key (sent as the X-API-Key header via API_HEADERS)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/YCloud-Developers/ycloud-whatsapp-mcp-server.git
cd ycloud-whatsapp-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"ycloud-whatsapp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_YCLOUD_WHATSAPP_MCP_SERVER>/build/index.js"
],
"env": {
"API_BASE_URL": "https://api.ycloud.com/v2",
"API_HEADERS": "X-API-Key:<YOUR_API_KEY>"
}
}
}
}<YOUR_PATH_TO_YCLOUD_WHATSAPP_MCP_SERVER>/build/index.js is the full (absolute) path to build/index.js in your clone — npm run build creates it. <YOUR_API_KEY> is your YCloud API key from the developer page of the YCloud console.
