Bring Conversational Commerce
to Cursor
Learn how to connect Blip to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Blip MCP Server?
What you can do
- Send WhatsApp and Chatbot messages directly to your customers.
- Create, update, and retrieve detailed contact information.
- Monitor support tickets from Blip Desk and manage ongoing conversation threads.
- Analyze active conversations to trigger personalized workflows.
How it works
1. Log in to your Blip portal and access your bot's settings. 2. Copy the API Key from the Connection Information area. 3. Securely connect your agent to start managing Blip communications instantly.Who is this for?
Customer Support teams managing tickets, Marketing teams triggering proactive messages, and Sales professionals following up on leads via WhatsApp.Built-in capabilities (10)
Create or update a Blip contact
Delete a Blip contact
Get a Blip contact by ID
Get messages from a Blip thread
Get a Blip desk ticket by ID
List Blip contacts
List Blip conversation threads
List Blip desk tickets
Ping the Blip bot
Send a message to a Blip contact
Why Cursor?
Cursor's Agent mode turns Blip into an in-editor superpower. Ask Cursor to generate code using live data from Blip and it fetches, processes, and writes. all in a single agentic loop. 10 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
Blip in Cursor
Blip and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Blip 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 Blip in Cursor
The Blip 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 10 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
Blip for Cursor
Every tool call from Cursor to the Blip MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the AI Agent manage ongoing Chatbot threads?
Yes, the agent can list active threads and retrieve their messages to understand the full context of a customer's conversation.
Is it possible to reply to customer support tickets on Blip Desk?
The AI agent can retrieve and analyze tickets from Blip Desk and send direct messages to the user via the send_message tool to assist with resolutions.
Can I use the agent to send automated WhatsApp notifications?
Absolutely. The agent can use the messaging capabilities to trigger plain text messages directly to phone numbers connected to your Blip router.
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.