The Plan Review MCP is a remote server that checks an AI coding agent's implementation plan against your codebase's real conventions before any code gets written. It runs as a Model Context Protocol server, so Claude Code, Cursor, Codex, and any MCP-capable agent can call it directly during planning, catching drift, duplication, and unsafe schema changes before they exist, not after a pull request opens.
Four skills are live today. full-review runs all twelve plan-check dimensions and is the default — run it on every plan before writing code. The other three are narrower, cheaper follow-up checks for a specific question mid-task.
| Skill | When to use it | Cost |
|---|---|---|
| full-review | Review this PRD/spec against our codebase — the default. | Included |
| architecture-fit | Does this plan fit how our codebase is built? | Included |
| schema-review | Is this migration safe? | Included |
| security-review | What's the threat surface of this plan? | Included |
Six plan-review tools cover that workflow: discovering which skills exist, reading a skill's full instructions, resolving project context, running a review, fetching a persisted result, and looking up a project by name. The same server also exposes the five Feature Factory cockpit tools listed below.
| Tool | Purpose |
|---|---|
| list_skills | List available plan-review skills plus planned ones. |
| get_skill | Full markdown instructions for a named skill. |
| get_project_context | Stack profile, ADR titles, module directories, and the skill registry for a project. |
| vibecop_check | Run a skill against a submitted plan and extracted intents; returns verdict, findings, recommendations. |
| get_plan_review | Fetch a persisted plan review by id. |
| resolve_project | Look up projects by name; returns candidates when ambiguous, never silently picks one. |
Five additional tools drive the Feature Factory from the same MCP server: create a graph-grounded feature run, read its live state, claim and report on individual task nodes, and approve or cancel the run at its human gate. Every MCP-capable agent gets identical behavior — no client is privileged.
| Tool | Purpose |
|---|---|
| feature_start | Create a feature run from a title + task list with expected footprints. |
| feature_status | Live run view: every node's state, edges, PR and issue numbers. |
| node_claim | Claim a ready node — returns the working branch and a 60-minute lease. |
| node_report | Report the branch pushed and PR open — the only self-reported status. |
| gate_approve | Approve the task graph (G1), or cancel the run. |
Mint a token in VibeCop Settings under "Plan Review MCP · Agent Auth," then add the server to your agent's MCP config. The full installer has copy-paste setup for Claude Code, Codex, and Cursor.