The Voiceflow MCP server is a remote Model Context Protocol server that gives Claude Code direct access to your Voiceflow projects. Once it’s connected, Claude can list your projects, read prompts and functions, pull transcripts, run evaluations, and make changes on your behalf, all without leaving your terminal.
It’s a remote server that uses OAuth, so there are no API keys to copy or rotate. You sign in to Voiceflow once in your browser, and Claude Code caches and refreshes the token for you.
This guide connects the Voiceflow MCP server to Claude Code. By the end, it will be ready to use.
Before you start
You’ll need:
- Claude Code installed on your machine, either the terminal CLI or the desktop app.
- A Voiceflow account. You’ll sign in to it during setup, and Claude acts on the projects that account can access.
Set up the Voiceflow MCP server
You can connect the server from the command line or from the Claude desktop app. Either way leaves you with the same connection.
These steps need a local Claude Code install. They won’t work in Claude Code web or cloud environments, which don’t provide the claude command or the /mcp command.
Add the server
Run the following command in your terminal to register the Voiceflow MCP server. Run it directly from your terminal, not inside a Claude Code session.
This connects the server in your current project. To make it available across all your projects, add --scope user to the command.
Open the MCP menu
Start Claude Code, then run the /mcp command. You’ll see voiceflow listed with a status indicating it needs authentication.
Start the sign-in flow
Select voiceflow, then choose Authenticate. Claude Code opens your browser to the Voiceflow sign-in page.
Sign in to Voiceflow
Sign in and approve the request. Your browser redirects back to Claude Code to confirm the connection. If the browser doesn’t open on its own, copy the URL Claude Code prints and open it manually.
You are approving two scopes, universal.workspace.read and universal.workspace.write. Claude Code asks for both because it edits projects as well as reads them. See what you are approving for what each one covers.
Verify the connection
To confirm everything is working, run:
The voiceflow server should appear as connected. You can also run /mcp inside a session to see its live status and the number of tools it exposes.
Claude Code stores the token securely and refreshes it automatically, so you won’t need to repeat this unless you disconnect the server or revoke access in Voiceflow.
Open Connectors
In the Claude desktop app, open Customize, then go to Connectors.
Add a custom connector
Click the + button and choose Add custom connector. Enter Voiceflow as the Name and https://mcp.voiceflow.com/mcp as the Remote MCP server URL, then click Add.
Connect
Voiceflow now appears under Not connected with a CUSTOM label. Select it, then click Connect.
Authorize in your browser
Your browser opens the Voiceflow consent page. Click Allow to grant Claude access to your workspaces. The connector then shows as connected in the Claude app.
Try it out
Once everything is setup, you’re ready to start using Voiceflow through Claude Code. Just describe what you want in plain language, for example:
Or:
Maintenance
The MCP server is hosted, so it updates automatically. There’s nothing to install or upgrade.
Reconnect or remove the server
If you ever need to sign in again, for example after revoking access in Voiceflow, run /mcp, select voiceflow, and clear the authentication. The next time you use the server, Claude Code prompts you to sign in again.
To remove the server completely, run: