Bring Chatbot
to Cline
Learn how to connect Landbot to Cline 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 Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Landbot tool calls without waiting for prompts between steps. Connect 12 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Landbot in Cline
Landbot and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Landbot to Cline 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 Cline
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 Cline 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 Cline
Every tool call from Cline 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.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.