# mcp-protocol-specialist

A subagent for Model Context Protocol work: transports, JSON-RPC 2.0, versioning and compliance across implementations.

- subagent · `type=agent` · Claude Code · 781 installs
- Author: davila7
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/davila7/claude-code-templates/tree/HEAD/cli-tool/components/agents/mcp-dev-team/mcp-protocol-specialist.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/agents/mcp-protocol-specialist

## What it does

This subagent knows the Model Context Protocol specification: how transports are built, how capabilities and versions get negotiated, how schemas are validated. Its toolset is narrow — `Read`, `Write`, `Edit` and `WebSearch` — so it will not run your code or your test suite.

Reach for it when you are building an MCP server or client and hit a transport mismatch. It works specification-first, suggests backward-compatibility and migration paths between versions, and produces spec documents and RFCs, transport implementation guides, schema validation frameworks, compliance test suites and migration guides.

One catch: without other tools it only sees what you put in files or what `WebSearch` turns up. If you need a live code walkthrough with execution, look elsewhere.

## Install

### Claude Code (native platform)

1. **claude-code-templates**
```bash
npx claude-code-templates@latest --agent mcp-dev-team/mcp-protocol-specialist
```

2. **Manually: put the files in place**
- File: `.claude/agents/mcp-protocol-specialist.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-specialist.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-specialist.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/davila7/claude-code-templates/tree/HEAD/cli-tool/components/agents/mcp-dev-team/mcp-protocol-specialist.md

## When to use it
- design a transport for a new MCP server
- align protocol versions between client and server
- check a schema against the specification
- write a migration guide for a new MCP version
- document edge case behaviour in an RFC

## Example prompts
- Help me design a Streamable HTTP transport for my MCP server
- Check my tool schema against the MCP specification
- Write a migration guide between protocol versions

## Similar
- [crypto-protocol-diagram](https://affpapa.org/en/nevibecode/skills/crypto-protocol-diagram.md) — skill · 3900 installs
- [open-responses](https://affpapa.org/en/nevibecode/skills/open-responses.md) — skill · 316 installs
- [mcp-developer](https://affpapa.org/en/nevibecode/skills/mcp-developer.md) — skill · 4200 installs
- [omni-agents-a2a](https://affpapa.org/en/nevibecode/skills/omni-agents-a2a.md) — skill · 977 installs
- [copilot-sdk](https://affpapa.org/en/nevibecode/skills/intellectronica-copilot-sdk.md) — skill · 531 installs
- [solana-rpc](https://affpapa.org/en/nevibecode/skills/solana-rpc.md) — skill · 451 installs

From the same set: [davila7/claude-code-templates](https://affpapa.org/en/nevibecode/by/davila7/claude-code-templates.md) — 205 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