Connect your WhatsApp Business Account (WABA) and CRM database to Claude, Cursor, ChatGPT, and AI agents with zero code using the open Model Context Protocol.
Step-by-step guides for Claude, Cursor, ChatGPT, Claude Code, and Windsurf.
Full input schemas, REST endpoint mappings, and safety policies for every ability.
Copyable natural language prompts for inbox triage, deal updates, and broadcasts.
The Chatofy MCP server connects your WhatsApp Business Account (WABA) and CRM database to the AI assistant you already use. Once connected, you run your WhatsApp business by asking in plain English:
“Send Rahul a WhatsApp message saying his order #4812 shipped today with our tracking link.”
“Who messaged us in the last 2 hours and hasn't had a reply from our team?”
“Tag everyone who asked about wholesale pricing as Hot Lead and create an enterprise deal.”
The assistant works out which Chatofy actions those need, shows you what it is about to do, and executes it securely on your account.
https://app.chatofy.in/api/mcp, authenticate with 1 click, and the assistant gains 32 Chatofy WhatsApp CRM abilities.Each application has its own dedicated step-by-step setup guide with copyable settings:
1-Click browser OAuth login. Free, Pro, Team & Enterprise plans.
Native MCP in .cursor/mcp.json for full CRM agent capability.
Connect in one terminal command with automatic OAuth sign-in.
Custom GPT Actions and hosted Streamable HTTP endpoint.
Native HTTP MCP integration for Cascade and Agent flows.
Connect GitHub Copilot Chat to Chatofy using Streamable HTTP.
Google terminal agent connected via Bearer API authentication.
Zed, Cline, n8n, Make, and all RFC-compliant HTTP MCP clients.
The assistant acts on your live CRM setup. If you haven't connected your WABA yet, complete onboarding in your dashboard.
Either 1-click browser OAuth login (Claude and Claude Code) or an API key from Settings → API Keys.
Claude Desktop, Cursor, ChatGPT, Claude Code, Windsurf, or VS Code. Each has its own dedicated page with exact clicks.
It's the same power, without the code. The Developer API is for developers who write a program that calls Chatofy. The MCP server is that API already wrapped up, so an AI assistant can use it for you.
| Comparison | Chatofy MCP Server | Developer API |
|---|---|---|
| Who it's for | Anyone who can type a message | Developers writing backend code |
| What you build | Nothing | Your own script, n8n flow or app |
| How you use it | Ask the assistant in English | Write code, run HTTP requests |
| Setup | Add URL in AI app, sign in once | Read API docs, construct payloads |
Send plain text, media attachments (PDFs, images, videos), and approved Meta templates. Send messages with up to 3 interactive reply buttons. Check whether a message was delivered or read.
Look someone up by phone or ID, add a contact, update custom attributes, read recent conversation transcripts, and check whether they are within the customer service window.
Create tags and apply them, list sales pipelines, create deals with revenue values, move deals across pipeline stages, and resolve or archive conversations.
Trigger automated visual chatbot flows, draft new message templates and submit them to Meta for approval, and review campaign delivery metrics.
There are 32 abilities in total. The complete list and schema for every tool is on the Tools Reference, and Things to Ask has conversational prompts that work.
This is WhatsApp's rule, not Chatofy's, and the AI cannot bypass it:
So asking the assistant to message someone who last contacted you three days ago requires an approved template. If you ask for plain text, WhatsApp rejects delivery. The assistant checks this window before trying.
Nothing extra from Chatofy. The MCP server uses your existing organization plan and its limits: your subscriber allowance, your message credits, and Meta's standard conversation charges. Your AI app's own plan is separate.
No. With Claude or Cursor you click through a few settings and authenticate. There is no code anywhere in that process.
With browser sign-in, Chatofy verifies your workspace when you connect. The hosted MCP server holds no credentials. You can revoke all connected clients at once by regenerating your API key in Settings → API Keys.
Yes. Each team member connects in their own AI app. Actions execute under their authorized organization workspace permissions.
Not by default. Claude, ChatGPT, Cursor, and VS Code ask for confirmation before any tool call that sends a message or modifies records.
No. Your Chatofy chatbots keep answering customers automatically, around the clock. The MCP server is for you: a way to run your CRM by asking instead of clicking through dashboards.