mcps

Recipe

PR review with Claude + GitHub MCP

Stop context-switching between your editor and GitHub. Claude reads diffs, spots bugs, and suggests fixes in the same chat.

10 minutes beginner 1 connector for Developers who don't want to context-switch between editor and GitHub for every diff

What you'll need

GitHub Reads PRs, diffs, and repo context so Claude can review like a teammate.
Required

Do this, in order

  1. 1

    Install GitHub MCP

    Add GitHub MCP to Claude Desktop using your GitHub personal access token.

    You'll get: Claude confirms GitHub MCP is installed and authenticated. You can list repos.

  2. 2

    Point Claude at the PR

    Review PR #142 in my-org/api-service — look for security issues and suggest improvements.

    You'll get: Claude pulls the diff, the description, and the changed file context, then returns a structured review.

  3. 3

    Get an AI-powered review

    Give me the top 3 risks in this PR, ordered by severity, with the exact lines they apply to.

    You'll get: A short ranked list with file:line references and an explanation per item.

  4. 4

    Ask follow-up questions

    Why might the authentication change in this PR cause issues with our existing token refresh logic?

    You'll get: Claude reads the surrounding files (not just the diff) and explains the interaction.

You're done when

Faster, more thorough code reviews without leaving your AI assistant — typically a 10-minute pass instead of a 30-minute scroll.

Why this workflow exists

Most code review time is spent loading context: opening the PR, scrolling the diff, jumping to related files, scanning the description. The actual judgment — is this change safe? — takes a few minutes. GitHub MCP collapses the loading time so you can spend the budget on judgment.

What success looks like

You paste a PR reference into Claude. You read a structured review with the top risks called out. You ask one or two follow-ups. You leave a comment on the PR. Total: ~10 minutes per review.