Use Claude Code, Codex, Cursor, or another supported assistant to work with Voiceflow in plain language. The setup prompt connects your account, makes documentation available, and installs Voiceflow skills where your client supports them.

Before you begin

Have a Voiceflow account and access to the workspace you want to use.
Open your AI assistant. For local installation, run it on the computer where you want to use Voiceflow.

Connect your assistant

Choose Setup prompt for guided setup of your Voiceflow connection, documentation access, and skills. Use CLI or your coding agent’s tab for manual connection instructions.

Setup prompt
Claude Code
Codex
Cursor
CLI

Paste this prompt into your AI assistant:

Setup prompt

Set up Voiceflow by following https://www.voiceflow.com/agents/setup

Your assistant will reuse existing connections or set up CLI or MCP access, connect Voiceflow’s documentation, and install the Voiceflow skills where your client supports them. Complete browser sign-in when prompted; your assistant will verify the connection before finishing.

Add Voiceflow

Run this command in your terminal:

claude mcp add --transport http voiceflow https://mcp.voiceflow.com/mcp

Open Claude Code, run /mcp, select voiceflow, and choose Authenticate. Sign in to Voiceflow in your browser and approve the connection.

Connecting grants your client access to read and change the projects your account can access. MCP authentication explains the permissions.

Confirm the connection

Ask Claude Code:

List my Voiceflow projects.

A project list confirms the connection is working.

Add Voiceflow

Run this command in your terminal:

codex mcp add voiceflow --url https://mcp.voiceflow.com/mcp

If adding the server already completed sign-in, continue to the next step. Otherwise, run:

codex mcp login voiceflow

Connecting grants your client access to read and change the projects your account can access. MCP authentication explains the permissions.

Confirm the connection

Ask Codex:

List my Voiceflow projects.

A project list confirms the connection is working.

Add Voiceflow

Add this configuration to .cursor/mcp.json in your project, or merge the voiceflow entry into your existing mcpServers:

{
  "mcpServers": {
    "voiceflow": {
      "url": "https://mcp.voiceflow.com/mcp"
    }
  }
}

When Cursor prompts you to authenticate, sign in to Voiceflow in your browser and approve the connection.

Connecting grants your client access to read and change the projects your account can access. MCP authentication explains the permissions.

Confirm the connection

Ask Cursor:

List my Voiceflow projects.

A project list confirms the connection is working.

Run these commands yourself in your local terminal.

Install the Voiceflow CLI

On macOS or Linux:

curl -fsSL https://raw.githubusercontent.com/voiceflow/cli/master/scripts/install.sh | bash

On Windows, use PowerShell:

iwr -useb https://raw.githubusercontent.com/voiceflow/cli/master/scripts/install.ps1 | iex

vf auth login

Follow the sign-in instructions in your terminal.

Confirm the connection

vf workspace list --output-format json

A workspace list confirms the connection is working. If you use a personal or service key, access depends on that key’s permissions; see CLI authentication.

What gets connected

Connection	What it enables
Platform access	Read and manage Voiceflow resources through an existing connection, the CLI, or the platform MCP server.
Documentation	Find Voiceflow guidance through the docs MCP server, with a supported fallback when the host cannot connect it.
Voiceflow skills	Give supported assistants reusable guidance for setup and working with Voiceflow.

Account access follows the permissions of your connected account or credential. Review MCP authentication or CLI authentication for details.

Try your first task

Start with a request that reads your project before making changes:

First task

List my Voiceflow projects and ask me which one to use. Then summarize that agent’s instructions and knowledge sources without making changes.

Check that your assistant is using the project you selected. Once it can inspect the agent, ask it to help with a specific prompt, knowledge source, or workflow.

If you get stuck

Sign-in did not finish: retry the browser flow in your assistant. See CLI authentication or MCP authentication for the connection you are using.
Tools do not appear after connecting: follow your client’s setup guide: Claude Code, Codex, or Cursor.
Skills are unavailable: support depends on the app. Use the setup prompt so your assistant can check its actual capabilities and explain what it configured.