mcp-reviewer — Claude Code subagent: MCP server review, how to install
mcp-reviewer reviews MCP server changes: tool schemas, safety gates on destructive calls, error handling and stdio correctness. Useful before you merge work on a server.
MIT ★ 1,198 updated 2026-10-23
.claude/agents/mcp-reviewer.mdWhat mcp-reviewer does
A reviewer subagent aimed at MCP servers. It reads the diff for tool names and how strict their schemas are, checks whether mutating and destructive calls sit behind a confirmation gate, and looks at timeouts, retries and error paths in the API client.
It runs on opus with four tools: Read, Grep, Glob, Bash. Stdio gets its own pass, since a server should log to stderr only. Anything written to stdout corrupts the message stream, and the review calls it out. The host config and runbook are checked against what actually runs.
You get findings sorted by priority, file references and commands to verify each one. Drop the file at .claude/agents/mcp-reviewer.md for Claude, or .codex/agents/mcp-reviewer.toml for Codex. MIT licensed, from hoangsonww/Claude-Code-Agent-Monitor.
What it helps with
- check that destructive MCP tools sit behind a safety gate
- catch stdout logging that breaks the stdio protocol
- tighten tool schemas and rename confusing tools
- add timeouts and retries to the server's API client
- match the host config and runbook to the real launch commands
Example prompts for the agent
- Run
mcp-revieweron the MCP server diff and list findings by priority - Review the tool schemas and safety gates in
src/server.ts, with file references - Check stdio logging: is anything going to stdout?
How to install mcp-reviewer
Manually: put the files in place
.claude/agents/mcp-reviewer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/mcp-reviewer.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-reviewer.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-reviewer
How do I install mcp-reviewer in Claude Code?
Copy the subagent file into your project at .claude/agents/mcp-reviewer.md. That is the whole install; it then shows up under the name mcp-reviewer.
What does mcp-reviewer do?
It audits changes to an MCP server: tool names and schemas, gates on mutating and destructive operations, timeouts and retries in the API client, stderr-only logging, and whether the host config and runbook match reality. Output is prioritised findings with file references.
Which model and tools does mcp-reviewer use?
opus, with access to Read, Grep, Glob and Bash. That covers reading server code, searching the repo and running verification commands.
Source text
mcp-reviewer.md · MIT
--- name: mcp-reviewer description: Review MCP server changes for tool safety, schema quality, and host integration correctness. tools: Read, Grep, Glob, Bash model: opus --- You are an MCP-focused reviewer for this repository. Focus on: - Tool naming and schema strictness. - Safety gate enforcement for mutating/destructive operations. - API client timeout/retry/error handling. - Stdio protocol safety (stderr-only logs). - Host configuration and runbook documentation accuracy. Output: - Prioritized findings. - File references. - Verification commands to run.
© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor