ycloud-whatsapp

This MCP server automatically generates MCP tools from the YCloud WhatsApp OpenAPI specification, enabling AI models to interact with the YCloud WhatsApp API directly. It supports all API endpoints, API authentication, parameter validation, HTTP request/response handling, and dynamic tool generation based on the OpenAPI spec. To use it, configure the server with the proper environment variables (API_BASE_URL and API_HEADERS) so that authorized requests can be made to YCloud. When integrated with Claude or other MCP-enabled clients, you can invoke the generated MCP tools to perform actions such as sending messages, querying account information, and managing WhatsApp templates, all through natural-language prompts that map to API calls.

• Prerequisites:

  • Node.js v16.0.0 or higher
  • npm v7.0.0 or higher
  • Access to a YCloud account and API key

• Steps:

  1. Clone the repository git clone https://github.com/YCloud-Developers/ycloud-whatsapp-mcp-server.git cd ycloud-whatsapp-mcp-server
  2. Install dependencies npm install
  3. Build the project npm run build
  4. Run the server (example with environment variables) API_BASE_URL=https://api.ycloud.com/v2
     API_HEADERS="X-API-Key:your-api-key-here"
     npm start

• Optional Claude integration:

  • Update Claude desktop config to point to the built MCP server index.js as shown in the repository's Claude integration guide

• Environment variables:
  • API_BASE_URL: Base URL for YCloud API (default: https://api.ycloud.com/v2)
  • API_HEADERS: Additional headers for API requests formatted as key:value pairs, e.g., X-API-Key:your-api-key
• Common issues:
  • Ensure Node.js and npm versions meet minimum requirements
  • Verify API key has the required permissions for the endpoints you intend to use
  • If the MCP server fails to load tools, re-build and confirm the OpenAPI spec URL/path is accessible
• Configuration tips:
  • You can modify OPENAPI_SPEC_PATH or API_BASE_URL to switch between environments (staging/production)
  • For Claude integration, ensure the path to build/index.js matches your build output
• Debugging:
  • Check server logs for runtime errors
  • Use MCP Inspector to inspect generated tools and endpoints