Skip to content

Pin the account MCP to version=2 (0.5.0) - #10

Merged
z4o4z merged 1 commit into
voiceflow:mainfrom
z4o4z:evgeny/pin-mcp-v2
Nov 10, 2026
Merged

z4o4z merged 1 commit into
voiceflow:mainfrom
z4o4z:evgeny/pin-mcp-v2

Conversation

@z4o4z

@z4o4z z4o4z commented Nov 10, 2026

Copy link
Copy Markdown
Member

What changes

  • The account MCP URL in the setup guide and in scripts/chat_eval.py is now https://mcp.voiceflow.com/mcp?version=2.
  • The setup guide has one sentence saying version=2 keeps the current tool names that the skills use.
  • The plugin version goes from 0.4.2 to 0.5.0 in the four plugin manifests and in the version line of voiceflow/skills/voiceflow/references/documentation.md.
  • CHANGELOG.md has a 0.5.0 entry.

The docs MCP URL (https://www.voiceflow.com/docs/mcp) is unchanged.

Why

The MCP v3 stack in creator-app (COR-15705, https://app.graphite.com/github/pr/voiceflow/creator-app/24073) makes https://mcp.voiceflow.com/mcp with no version serve the new vf_* tools. The skills here still name the v2 voiceflow_* tools. Until the skills move, users must connect with ?version=2.

A follow-up major release moves the skills to the v3 tool names and drops the pin.

Verification

  • python3 scripts/validate.py passes.
  • python3 -m unittest discover -s tests -v passes (98 tests, 1 skipped).
  • python3 scripts/build.py succeeds.
  • scripts/scan_secrets.py not run: Gitleaks is not installed locally. CI runs it.

🤖 Generated with Claude Code

The MCP server default is moving to v3 tool names (COR-15705). The skills
still name the v2 tools, so the account MCP URL now carries version=2.
Bump the plugin to 0.5.0 in every manifest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@z4o4z
z4o4z requested a review from Bradenream as a code owner November 10, 2026 12:07
@z4o4z
z4o4z merged commit bf94ff1 into voiceflow:main Nov 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant