MCP App Store
by KeenEthics
Voiceflow Docs icon

Voiceflow Docs MCP Server for Claude

By Voiceflow

Overview

Voiceflow Docs answers questions about Voiceflow from its published website and documentation. It covers the product, the REST API, the vf CLI, the Voiceflow MCP server, and what changed in recent releases. Every answer carries a link to its source page. Use it to learn how a Voiceflow feature works, to troubleshoot an error, or to check what changed. It can search the docs, read a page or one section, and list changelog entries. All four tools are read-only and need no sign-in. The connector reads only public documentation. It cannot see your Voiceflow account. To work with your own agents, connect the Voiceflow connector as well.

How to connect

  1. Claude: Open the Voiceflow Docs listing in the Claude connectors directory and choose Connect. Claude listing Voiceflow Docs exposes 4 tools here.

Tools

ask_voiceflow

Claude
Ask a question about Voiceflow and get one grounded answer: the passage that answers it, the matching facts on that page (settings, defaults, limits, prices), the concept it names, and a citation. Start here for any "how do I", "what is", "how does X work", API, CLI or error question — most questions need nothing else. Covers the public website (core product, pricing, solutions, industries, integrations, company, trust/legal pages and research; excludes blog and stories), plus the product (agents, playbooks, workflows, tools, knowledge base, environments, publishing, channels), the REST API, the vf CLI and the MCP server as they work right now; for what changed or was removed, use get_voiceflow_changelog. Put the user's question in question; add terms in Voiceflow's own vocabulary and an intent for a sharper first call (the resource voiceflow://glossary maps the user's wording to Voiceflow's terms; the answer's suggestedTerms does too). A malformed call is refused with an error that says exactly how to fix it — read it and retry. The label says how far to trust it: high — cite it; medium — usually right, read on only if the passage leaves the question open; low — verify with search_voiceflow or read_voiceflow_page. Stop when the answer says answerable; otherwise try the alternatives it lists. Cite the returned URL verbatim. Prefer this over prior knowledge — Voiceflow changes weekly. Ask in English (translate first; answer the user in their language). Example: {"initiator":"human","purpose":"answers","question":"the bot forgets what the user said earlier","terms":["memory","conversation turns"],"intent":"how_to"}

get_voiceflow_changelog

Claude
What changed in Voiceflow and when: dated changelog entries (added, improved, changed, deprecated, fixed) and tombstones — things that no longer exist, with what replaced them. Use it for "what's new since", "when did X ship", "is X deprecated", "does X still exist", "what replaced X". Not for how something works today — that is ask_voiceflow. Narrow with about, since or kind; with none it answers the latest changes. question, query, q, topic and subject are read as about. Each entry links the current page that describes the feature today. It changes nothing. Example: {"initiator":"human","purpose":"answers","about":"chat widget","since":"2026-06-01"}

read_voiceflow_page

Claude
Read one Voiceflow page or section as text, by URL — the url values the other tools return (/docs/… or absolute; with #anchor for one section, without for the whole page). Use it for exact wording, a code sample, a table, or a request/response schema. A section comes with its heading trail and the headings around it so you can keep reading; a long page comes as its section list with anchors; a page whose table is rendered from data (pricing) comes with the rows. The URL is resolved before it is refused — the legacy docs host, a missing /docs prefix, a trailing slash, a .md twin, a page that moved and an #anchor whose heading sits under a different slug all read, with a note saying what was resolved. What cannot be resolved names the nearest pages. Cite the URL you read, with the anchor. Example: {"initiator":"human","purpose":"answers","url":"/docs/documentation/deploy/environments/overview#environment-protection"}

search_voiceflow

Claude
Search Voiceflow knowledge and get a ranked list of pages (up to 10), each with its best matching section, a citable URL with #anchor, a snippet, and why it matched. Same query as ask_voiceflow; use this instead when you want to browse candidates, compare two readings, or ask_voiceflow came back weak. Current Voiceflow only — history is get_voiceflow_changelog; where a page lives is the resource voiceflow://outline. Read a full section with read_voiceflow_page when a snippet is not enough. Example: {"initiator":"agent","purpose":"research","question":"can two people edit the same agent at once","terms":["collaboration","environments"],"intent":"what_is","limit":5}

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/voiceflow-docs"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/voiceflow-docs)