WhatsApp MCP server for Cursor, VS Code, Gemini CLI and Codex

If you build with an AI coding assistant, you can give it WhatsApp: send a test notification while you develop, submit the template your app needs, or check delivery status — without leaving the editor. SendFromChat is a hosted MCP server for Meta's official WhatsApp Cloud API, so there's nothing to run locally.

Why a hosted MCP server

You could call Meta's Graph API directly, but you'd be rebuilding the parts that take time: token storage, template validation, the 24-hour window rules, webhook handling, pacing under messaging limits, opt-out tracking. A hosted server gives your assistant all of that as tools, over streamable HTTP — the transport every current MCP client supports.

Your connector URL looks like https://sendfromchat.com/api/mcp/YOUR_KEY. Get it from the Connect your AI assistant card in the SendFromChat dashboard. Alternatively use https://sendfromchat.com/api/mcp with an Authorization: Bearer YOUR_KEY header, if your client supports headers.

Cursor

Settings → MCP → Add new MCP server, or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "sendfromchat": { "url": "https://sendfromchat.com/api/mcp/YOUR_KEY" }
  }
}

VS Code (GitHub Copilot, Agent mode)

Command Palette → MCP: Add Server → HTTP, paste the URL, name it sendfromchat. Or in .vscode/mcp.json:

{
  "servers": {
    "sendfromchat": { "type": "http", "url": "https://sendfromchat.com/api/mcp/YOUR_KEY" }
  }
}

Windsurf

In ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "sendfromchat": { "serverUrl": "https://sendfromchat.com/api/mcp/YOUR_KEY" }
  }
}

Gemini CLI

In ~/.gemini/settings.json:

{
  "mcpServers": {
    "sendfromchat": { "httpUrl": "https://sendfromchat.com/api/mcp/YOUR_KEY" }
  }
}

Start gemini and run /mcp to confirm it's connected.

Codex

In ~/.codex/config.toml:

[mcp_servers.sendfromchat]
url = "https://sendfromchat.com/api/mcp/YOUR_KEY"

Claude Code

claude mcp add --transport http sendfromchat https://sendfromchat.com/api/mcp/YOUR_KEY

Anything else

Any MCP client that supports remote servers over streamable HTTP works: add a server, choose HTTP, paste the URL. If your client only supports local (stdio) servers, use a small bridge such as mcp-remote.

Useful developer prompts

• "Send the hello_world template to my number to check the integration."
• "Create a UTILITY template for password-reset codes in English and Spanish and tell me when they're approved."
• "Is my webhook receiving delivery receipts? Show the last five messages and their status."
• "Upload test-users.csv as a list called staging_testers."

The full list of tools is in the MCP tools reference.

Security notes

• The key in the URL grants full access to your workspace. Keep configs with keys out of version control (use a user-level config, not a repo file), or use the header form with an environment variable where your client supports it.
• Regenerating the connector URL in the dashboard immediately disables the old one.