add-mcp-tool

Scaffold new MCP tools with matched handlers across VMAFx Go and Python servers.

3|1|Updated May 28, 2026
One-click install
npx skills add https://github.com/VMAFx/vmafx --skill add-mcp-tool-vmafx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-mcp-tool
Source: https://github.com/VMAFx/vmafx/tree/main/.claude/skills/add-mcp-tool
Command: npx skills add https://github.com/VMAFx/vmafx --skill add-mcp-tool-vmafx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the repetitive work of adding a new MCP tool in two codebases at once, helping the Go and Python servers stay synchronized without manual drift.

Core Features & Use Cases

  • Dual-surface scaffolding: Generates matched Go and Python handler stubs for the same tool name.
  • Parity enforcement: Adds registration, schema, tests, changelog notes, and per-tool documentation so both servers expose the same contract.
  • Use case: When a new VMAFx capability needs to appear in Claude Desktop or Cursor, this Skill creates the full tool surface and supporting files in one workflow.

Quick Start

Ask the assistant to add a new MCP tool named vmaf_score and then complete the generated Go, Python, test, and documentation stubs.

Frequently Asked Questions about add-mcp-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new MCP tool across Go and Python servers simultaneously?

Transport parity ensures Go and Python servers expose the exact same MCP tool contract, including identical JSON schemas and response shapes. Maintaining parity prevents manual drift between codebases when adding new capabilities for Claude Desktop or Cursor.

What is transport parity in MCP tool development and why does it matter?

Transport parity ensures Go and Python servers expose the exact same MCP tool contract, including identical JSON schemas and response shapes. Maintaining parity prevents manual drift between codebases when adding new capabilities for Claude Desktop or Cursor.

How do I add a new scoring or health tool to an MCP server without breaking parity?

Yes, you can use this scaffolding workflow for new scoring, tuning, model catalog, and health tool scenarios. It applies to any new VMAFx capability that must remain transport-parity compatible across Go and Python servers.

Does this MCP scaffolding workflow support both Go and Python server environments?

Yes, you can use this scaffolding workflow for new scoring, tuning, model catalog, and health tool scenarios. It applies to any new VMAFx capability that must remain transport-parity compatible across Go and Python servers.

What files and tests need to be updated when adding an MCP tool to maintain the project contract?

Adding an MCP tool requires updating registration code, JSON schemas, smoke tests, changelog notes, and per-tool documentation. These updates satisfy the project contract and ensure both Go and Python servers expose the same tool surface.