https://mcp.voiceflow.com/mcp that authenticates with OAuth, so there are no API keys to manage. You sign in to Voiceflow once, and the assistant acts on the projects your account can access.
The setup guide walks through connecting the server to Claude Code.
What you can do
The server exposes Voiceflow’s agent-management surface as tools, grouped by capability:| Area | What the assistant can do |
|---|---|
| Projects & environments | List projects, manage environments, publish, compile, export, and handle variables and secrets |
| Agent design | Edit the global prompt, agent instructions, and routing; create and update playbooks and workflows; configure model and voice behavior |
| Tools | Create and wire functions, API tools, MCP tools, and prebuilt integrations, at the agent or playbook level |
| Knowledge base | Manage documents and data sources, and run retrieval queries to test coverage |
| Testing | Run live test conversations through the Dialog Manager and automated end-to-end simulations |
| Measurement | Fetch and search transcripts, design and run evaluations, and query analytics and usage |
How it works
- Plain language, not tool names. Once connected, you don’t call tools directly. You describe what you want, for example “pull the last 50 transcripts for my support agent and find where it’s failing”, and the client picks the right tools.
- Namespaced tools. Every tool is exposed to the client as
mcp__voiceflow__*, so it never collides with other servers you’ve connected. - Scoped to your account. The assistant can only see and change the projects your signed-in Voiceflow account has access to.
Get started
Set up Voiceflow in Claude Code
Connect the MCP server to Claude Code and sign in with your account.