Bring Chatbot Builder
to VS Code Copilot
Learn how to connect Typebot to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Typebot data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Typebot in VS Code Copilot
Typebot and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Typebot to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.