npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@iflow-mcp/joaomj-code-reviewer-mcp

v0.1.0

Published

A Model Context Protocol server

Readme

Code Reviewer MCP Server

A GitHub Pull Request Code Review server using Model Context Protocol

This MCP server provides automated code review capabilities for GitHub pull requests by integrating with OpenRouter's AI models.

Features

  • Automated code reviews for GitHub pull requests
  • Detailed feedback on code quality, style and potential issues
  • Integration with OpenRouter's AI models (currently using Gemini 2.5 Pro)
  • Comprehensive logging for debugging

Requirements

  • A GitHub Personal Access Token (PAT) with repo scope for private repositories or public_repo scope for public repositories. This PAT is required to fetch pull request data.
  • An OpenRouter API Key.

Current Limitations

⚠️ Important: Currently this server only works with:

  • Open pull requests (not draft PRs)

Installation

  1. Clone this repository:
git clone https://github.com/joaomj/code-reviewer-mcp.git
cd code-reviewer-mcp
  1. Install dependencies:
npm install
  1. Set required environment variables:
export GITHUB_PAT=your_github_personal_access_token
export OPENROUTER_API_KEY=your_openrouter_api_key
  1. Build the server:
npm run build

Usage

To start the MCP server:

node build/index.js

The server will be available to any MCP-compatible client (like Claude Desktop).

Configuration

Add to your MCP client configuration:

{
  "mcpServers": {
    "code-reviewer-mcp": {
      "command": "node",
      "args": ["/path/to/code-reviewer-mcp/build/index.js"],
      "env": {
        "GITHUB_PAT": "your_github_token",
        "OPENROUTER_API_KEY": "your_openrouter_key"
      }
    }
  }
}

Development

For development with auto-rebuild:

npm run watch

To run tests:

npm test

Debugging

Use the built-in logging which outputs to stderr with detailed information about:

  • GitHub API requests
  • OpenRouter API calls
  • Processing steps
  • Any errors encountered

For more advanced debugging, use the MCP Inspector:

npm run inspector

Next Steps

Planned improvements and features:

  • [ ] Draft pull request analysis
  • [ ] Customizable review templates
  • [ ] Support for multiple AI models (OpenAI, Claude, etc.)
  • [ ] File-specific feedback
  • [ ] Rate limiting and caching

Contributing

Suggestions are welcome. Please open an issue first to discuss what you would like to change.