Bring Conversational Ai
to VS Code Copilot
Learn how to connect Voiceflow to VS Code Copilot 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 Voiceflow MCP Server?
Connect your Voiceflow account to any AI agent and simplify how you build, test, and monitor your conversational assistants through natural language conversation.
What you can do
- Agent Interaction — Send messages and trigger actions in your Voiceflow agents to test responses and flows instantly.
- Knowledge Base (RAG) Control — Query your agent's KB directly for answers and list uploaded documents and tags.
- State Management — Retrieve, update, or reset user conversation states and variables to debug complex logic.
- Transcript Analysis — List and fetch full conversation logs for any project to monitor user interactions.
- Operational Monitoring — Retrieve user feedback (upvotes/downvotes) and monitor project configurations in real-time.
How it works
1. Subscribe to this server
2. Enter your Voiceflow API Key and Version ID
3. Start managing your conversational ecosystem from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Conversation Designers — quickly test agent responses and query the knowledge base via simple AI commands.
- AI Developers — debug user states and inspect transcripts during the development and testing cycle.
- Product Managers — monitor user feedback and conversation logs directly from the workspace.
Built-in capabilities (12)
Reset user session
Get user feedback
Get project details
Get user conversation state
Get transcript details
Send message to Voiceflow agent
List KB documents
List KB document tags
List Voiceflow projects
List conversation transcripts
Ask the Knowledge Base
Update user state/variables
Why VS Code Copilot?
GitHub Copilot Agent mode brings Voiceflow data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 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
Voiceflow in VS Code Copilot
Voiceflow and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Voiceflow 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 Voiceflow in VS Code Copilot
The Voiceflow 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 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
Voiceflow for VS Code Copilot
Every tool call from VS Code Copilot to the Voiceflow MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I query my Voiceflow Knowledge Base directly via AI?
Yes! Use the query_kb tool with your question. Your agent will trigger the Voiceflow RAG system and return the answer based on your uploaded documents.
How do I see the transcripts for a specific project?
Run the list_transcripts query with your Project ID. The agent will return a list of past conversation logs, which you can then inspect using get_transcript.
Is it possible to reset a user's session via AI?
Absolutely. Use the delete_state tool and provide the User ID. This will permanently clear the conversation history and variables for that specific session.
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.