Code Review MCP Tool for Cursor

What is Code Review MCP Tool for Cursor?

Code Review MCP Tool for Cursor is a Model Context Protocol (MCP) server that provides automated code review and leaves GitHub PR comments for any app supporting MCP integration, such as Cursor.

How to use Code Review MCP Tool for Cursor?

Add an MCP server configuration in your app’s JSON file with command: "npx", args: ["-y", "code-review-mcp-server"], and required environment variables like GITHUB_TOKEN. Then send commands such as code review with a base branch or a GitHub PR URL to get diffs and review suggestions.

Key features of Code Review MCP Tool for Cursor

• Compare code differences between two git branches
• Compare code differences from GitHub pull request URLs
• Add summary and line-specific comments to GitHub PRs
• Retrieve review guidelines from Notion code blocks
• Read PR templates from local directories
• Create GitHub Pull Requests with auto-detected repository info

Use cases of Code Review MCP Tool for Cursor

• Perform local branch review before merging changes
• Automate code review and comment on GitHub pull requests
• Integrate with CI pipelines using n8n webhooks for automated review
• Provide consistent review instructions via local markdown files or Notion

FAQ from Code Review MCP Tool for Cursor

What are the prerequisites for using this tool?

Node.js v18 or above, Git installed, and either a GITHUB_TOKEN environment variable or the GitHub CLI (gh) installed and authenticated for PR operations.

How are review instructions prioritized?

The tool uses a priority order: 1) Local markdown file via LOCAL_INSTRUCTIONS_FILE_PATH, 2) Notion integration (requires NOTION_API_KEY), 3) Built-in default guidelines.

Can I use it with Cursor or other MCP apps?

Yes, it is an MCP server compatible with any app that supports MCP integration, including Cursor.

Does it require a GitHub token?

It is optional; the tool falls back to the GitHub CLI (gh) if GITHUB_TOKEN is not set.

Where does the review data live?

Code diffs are obtained from local git or GitHub PRs via the API. No external data storage is used by the server; PR comments are added directly to GitHub.