# mcp-protocol-wasp-drone

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.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/platform-and-release-tools/agents/mcp-protocol-wasp-drone.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/mcp-protocol-wasp-drone

## What it 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.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install platform-and-release-tools@wasp-nest
```

2. **Manually: put the files in place**
- File: `.claude/agents/mcp-protocol-wasp-drone.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/mcp-protocol-wasp-drone.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/mcp-protocol-wasp-drone.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/platform-and-release-tools/agents/mcp-protocol-wasp-drone.md

## When to use it
- 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
- 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

## Similar
- [mcp-protocol-specialist](https://affpapa.org/en/nevibecode/agents/mcp-protocol-specialist.md) — subagent · 781 installs
- [mcp-developer](https://affpapa.org/en/nevibecode/skills/mcp-developer.md) — skill · 4600 installs
- [MCP Protocol Conformance](https://affpapa.org/en/nevibecode/mcp/mcp-protocol-conformance.md) — MCP server
- [cli-a2a](https://affpapa.org/en/nevibecode/skills/cli-a2a.md) — skill · 1300 installs
- [omni-agents-a2a](https://affpapa.org/en/nevibecode/skills/omni-agents-a2a.md) — skill · 1300 installs
- [okx-agent-payments-protocol](https://affpapa.org/en/nevibecode/skills/okx-agent-payments-protocol.md) — skill · 16200 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
