Bring Chatbot
to Cursor
Learn how to connect Landbot to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Landbot MCP Server?
Connect your Landbot account to any AI agent and manage chatbots through natural conversation.
What you can do
- Bot Management — List bots, inspect configurations, and track performance
- Conversation Tracking — Browse conversations, read messages, and send replies
- Customer Database — List customers with engagement data and conversation history
- Flow Monitoring — Track chatbot flows and their conversion metrics
- Channel Management — Monitor WhatsApp, Web, and API channels
- Analytics — Access conversation metrics, response rates, and bot performance
How it works
1. Subscribe to this server
2. Enter your Landbot API Token
3. Start managing chatbots from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Marketing — manage lead-generation bots and track conversions
- Support — monitor customer conversations and response quality
- Growth — analyze chatbot performance and optimize flows
Built-in capabilities (12)
Check API status
Get user profile
Assign to human
List available bots
List chatbot users
Get event configs
List support agents
Send chat image
Send chat message
Send WA template
Start bot flow
Set user property
Why Cursor?
Cursor's Agent mode turns Landbot into an in-editor superpower. Ask Cursor to generate code using live data from Landbot and it fetches, processes, and writes. all in a single agentic loop. 12 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
Landbot in Cursor
Landbot and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Landbot 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 Landbot in Cursor
The Landbot 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 12 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
Landbot for Cursor
Every tool call from Cursor to the Landbot MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I manage bots and read conversations?
Yes. List all bots with performance metrics, browse conversations with full message history, and send replies to customers.
How does Landbot authentication work?
Landbot uses a Token header for authentication against api.landbot.io/v1. This differs from standard Bearer authentication.
Can I track chatbot conversion metrics?
Yes. Monitor flow completion rates, drop-off points, lead capture rates, and conversation-to-conversion metrics per bot.
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.