mcp-protocol-stinger — Claude Code skill: MCP server audit
mcp-protocol-stinger — a skill for designing and auditing MCP servers on Claude Code and Codex. Covers tools, schemas, transport, JSON-RPC errors, authentication, testing, and registration across four IDE harnesses.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat mcp-protocol-stinger does
mcp-protocol-stinger provides a procedural reference for building and verifying MCP server correctness against the specification, @modelcontextprotocol/sdk, and JSON-RPC 2.0. Eight guides address general questions: transport choice (stdio vs HTTP), tool and resource design, zod schemas, error models, capability negotiation, authentication, testing, and server registration in Claude Code, Cursor, Codex, and Cowork. A ninth guide walks through all principles applied to a real agent-memory MCP server.
The skill organizes around guides, audit templates, and worked examples. Each guide ties conclusions to a spec section or SDK symbol so developers verify the reasoning, not just accept it. Core directives: the zod import must be zod/v3 (v4 breaks schemas), tool names and argument shapes form a cross-harness contract (rename is breaking), and JSON-RPC errors must never be conflated with tool results.
What it helps with
- audit an MCP server for protocol and SDK correctness
- choose between stdio and HTTP transport for an MCP server
- design a tool, resource, or prompt with a correct schema
- route an error to the right channel: JSON-RPC or tool result
- register an MCP server in Claude Code, Cursor, Codex, or Cowork
Example prompts for the agent
- Design an MCP tool for agent memory search with zod/v3 schema and test example
- Audit this MCP server for stdio hygiene issues and zod v4 schema breaks
- How do I register an MCP server in both Claude Code and Cursor?
How to install mcp-protocol-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nestThis installs the whole platform-and-release-tools plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-protocol-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/mcp-protocol-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mcp-protocol-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-protocol-stinger -a codex2Manually: put the files in place
.agents/skills/mcp-protocol-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-protocol-stinger -a cursor2Manually: put the files in place
.cursor/skills/mcp-protocol-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/platform-and-release-tools/skills/mcp-protocol-stinger2Manually: put the files in place
.github/skills/mcp-protocol-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill mcp-protocol-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/platform-and-release-tools/skills/mcp-protocol-stingerManually: put the files in place
.devin/skills/mcp-protocol-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mcp-protocol-stinger
How do I install mcp-protocol-stinger in Claude Code?
Run in order: /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install platform-and-release-tools@wasp-nest, npx skills add legioncodeinc/vibe-coding-tools --skill mcp-protocol-stinger -a claude-code. The guide opens at ~/.claude/skills/mcp-protocol-stinger/SKILL.md.
What does mcp-protocol-stinger do?
It is a reference for building and auditing MCP servers. It includes guides on transport choice, tool design, zod schemas, JSON-RPC error handling, authentication, testing patterns, and registration in four IDE harnesses.
Why must I use zod/v3 instead of zod/v4?
The SDK generates tool JSON schemas from zod v3 internals. Version v4 produces an empty or incorrect schema, breaking parameter validation and tool execution.