Bring Whatsapp Api
to Cursor
Learn how to connect Wati to Cursor and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Wati MCP Server?
Connect your Wati WhatsApp Business account to any AI agent and simplify how you engage with your customers through natural conversation and automated messaging workflows.
What you can do
- Direct Messaging — Send instant WhatsApp session messages to active contacts for real-time support and engagement.
- Template Automation — Send pre-approved WhatsApp templates to start conversations or send notifications with dynamic parameters.
- Contact Management — List and inspect your WhatsApp subscribers and contacts to keep your directory up-to-date.
- Chat History — Retrieve the complete message history for any specific contact to understand the conversation context.
- Template Catalog — List all available message templates to identify the best options for your communication strategy.
How it works
1. Subscribe to this server
2. Enter your Wati API Key and API Endpoint (found in your Wati API dashboard)
3. Start managing your WhatsApp communication from Claude, Cursor, or any MCP client
Who is this for?
- Customer Support Teams — quickly respond to inquiries and retrieve chat history via simple AI commands.
- Sales & Marketing — automate the sending of template-based notifications and manage lead contacts directly.
- Operations Managers — monitor communication flows and verify template availability without leaving the workspace.
Built-in capabilities (13)
Add a contact
Verify connectivity
Get contact details
Get template details
List broadcasts
List contacts
List messages
List tags
List message templates
Send media message
Send a session message
Send a template message
Update contact attributes
Why Cursor?
Cursor's Agent mode turns Wati into an in-editor superpower. Ask Cursor to generate code using live data from Wati and it fetches, processes, and writes. all in a single agentic loop. 13 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Wati in Cursor
Wati and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Wati to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Wati in Cursor
The Wati MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Wati for Cursor
Every tool call from Cursor to the Wati MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is the difference between a session message and a template message?
Session messages can only be sent if the user has messaged you in the last 24 hours. Template messages are pre-approved by WhatsApp and can be used to initiate a conversation at any time.
How do I see the approved templates in my account?
Use the list_message_templates query. Your agent will retrieve the complete list of pre-approved WhatsApp templates available in your Wati dashboard.
Can I retrieve the last messages from a specific customer?
Yes! Use the list_chat_history tool and provide the customer's WhatsApp number. The agent will return the message history for that specific conversation.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.