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:What you are approving
Connecting the server grants an OAuth token covering both reading and changing your workspace. There is no API key, and no lesser grant that still produces a working session.How MCP authentication works
The two scopes, what each covers, and what a client has to support.
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.
- Standard OAuth, no shared secret. Authorization code with PKCE (
S256), refresh tokens for renewal, and the token sent as a bearer header. Clients can register themselves, so there is nothing to paste and nothing to rotate by hand.
Get started
Set up Voiceflow in Claude Code
Connect the MCP server to Claude Code and sign in with your account.