mcp-protocol-wasp-drone — Claude Code subagent: setup and use
mcp-protocol-wasp-drone — a subagent for designing and auditing MCP servers against the protocol spec. Useful when tuning tool contracts, transport modes, and client configs.
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-wasp-drone does
The subagent enforces specification compliance when building MCP servers using @modelcontextprotocol/sdk. It audits the boundary between tools, resources, and prompts, checks raw input shapes against zod compatibility issues across v3 and v4, and splits error messaging so protocol faults stay distinct from domain results.
It handles transport selection between stdio and Streamable HTTP, flagging any console writes to stdout that break JSON-RPC framing. The drone also prepares registration files across Claude Code .mcp.json, Cursor, and Codex TOML configurations. Subprocess sandboxing, TLS termination, and credential vaulting remain outside its operational boundary.
What it helps with
- audit tool definitions and input schemas against MCP specifications
- resolve zod version conflicts and JSON-RPC framing errors
- format MCP configuration blocks for Claude Code, Cursor, and Codex
Example prompts for the agent
- Audit this MCP server implementation for spec compliance
- Review the zod schemas for our MCP tool parameters
- Help me register this MCP server inside Codex TOML config
How to install mcp-protocol-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/mcp-protocol-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/mcp-protocol-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/mcp-protocol-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about mcp-protocol-wasp-drone
How to install mcp-protocol-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools in your terminal, then execute /plugin install platform-and-release-tools@wasp-nest.
What does mcp-protocol-wasp-drone do?
It reviews MCP servers for protocol correctness, inspects zod input schemas, guides transport choices, and writes configuration manifests for supported agent harnesses.
Does this subagent handle credential vaulting and TLS?
No, it limits its scope to protocol mechanics and tool contracts. Low-level process isolation, TLS setup, and credential storage are routed to separate drones.