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.
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.
- 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-Key` header
- The specification source itself overridable through `OPENAPI_SPEC_PATH`, which defaults to `https://docs.ycloud.com/openapi.json` — you can pin a local copy instead of fetching the live one
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`.
Build from source — clone the repository and build it, then point your client at the binary