The latest articles on DEV Community by Subsis (@subsis_dev). https://dev.to/subsis_dev https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3957150%2Fde39c9d8-c432-4f5b-9607-2882ce9bd639.png https://dev.to/subsis_dev en Subsis Thu, 28 May 2026 18:19:42 +0000 https://dev.to/subsis_dev/i-built-a-local-mcp-server-that-gives-claude-code-real-pr-context-33s-reviews-instead-of-90s-4g1n https://dev.to/subsis_dev/i-built-a-local-mcp-server-that-gives-claude-code-real-pr-context-33s-reviews-instead-of-90s-4g1n <h2> The problem with Claude Code PR reviews </h2> <p>I use Claude Code for almost everything. But PR reviews kept frustrating me.</p> <p>The workflow looks like this without tooling:</p> <ol> <li>Find the PR URL</li> <li>Run <code>gh pr diff</code> locally, copy ~800 lines</li> <li>Paste into Claude Code (often truncated mid-function)</li> <li>Ask for a review</li> <li>Get generic feedback: "this looks fine, consider adding error handling"</li> </ol> <p>What's missing? <strong>Blame context</strong> (who wrote this line, when, why), <strong>linked issues</strong> (what bug was this PR supposed to fix), and a <strong>structured review format</strong> that forces citations.</p> <p>Claude doesn't know any of that by default. You're asking it to review code with no archaeological context.</p> <h2> The fix: a local MCP server </h2> <p>MCP (Model Context Protocol) lets you give Claude Code tools that run locally on your machine. The server speaks JSON-RPC over stdio and Claude calls your tools the same way it calls built-in tools.</p> <p>I built a Node.js MCP server with 4 tools backed by <code>gh</code> CLI and local <code>git</code>:</p> claude ai productivity opensource