Bring Chatbot Builder
to Cursor
Learn how to connect Typebot to Cursor and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Typebot MCP Server?
Connect your Typebot account to any AI agent and simplify how you build, manage, and analyze your conversational assistants through natural conversation.
What you can do
- Bot Management — List all typebots across your workspaces and folders, and retrieve detailed metadata and flow structures.
- Deployment Control — Publish the latest bot changes to production instantly without leaving your agent.
- Result Analysis — List and export user submissions and conversation results to track leads and performance.
- Organization Oversight — Manage workspaces and folders to keep your conversational projects structured.
- Session Testing — Programmatically start new chat sessions to verify bot logic and user experiences.
How it works
1. Subscribe to this server
2. Enter your Typebot API Token (found in your account settings)
3. Start managing your conversational forms from Claude, Cursor, or any MCP client
Who is this for?
- Conversation Designers — quickly verify bot logic and publish updates via simple AI commands.
- Marketing & Sales Teams — monitor incoming results and export lead data directly from the workspace.
- Product Managers — get instant bird's-eye views of bot performance and organization folders via the AI assistant.
Built-in capabilities (8)
Permanently delete a typebot
Essential for reviewing the bot logic. Get details and structure for a specific typebot
Folders are used to group related typebots. List all folders in a workspace
Essential for data analysis and lead export. List collected user responses for a bot
Can be filtered by a specific workspace ID. List all conversational typebots
Workspaces contain folders and bots. List all accessible Typebot workspaces
Requires the unique bot ID. Publish and deploy the latest bot changes
Useful for testing bot flows or automated interactions. Programmatically start a new bot conversation
Why Cursor?
Cursor's Agent mode turns Typebot into an in-editor superpower. Ask Cursor to generate code using live data from Typebot and it fetches, processes, and writes. all in a single agentic loop. 8 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
Typebot in Cursor
Typebot and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Typebot 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 Typebot in Cursor
The Typebot 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 8 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
Typebot for Cursor
Every tool call from Cursor to the Typebot MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I publish a bot after making changes via AI?
Yes! Use the publish_typebot action and provide the unique bot ID. Your agent will instantly deploy the latest changes to the public URL.
How do I see the submissions or leads collected by a bot?
Run the list_typebot_results query with your Typebot ID. The agent will retrieve the complete history of user responses and collected data.
Is it possible to list bots from a specific workspace?
Absolutely. Use the list_typebots tool and provide the optional workspace_id to retrieve only the bots associated with that team area.
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.