MCP Server - Code Review

Created By
arahismana year ago
Overview

what is MCP Server - Code Review?

MCP Server - Code Review is a server implementation for the Model Context Protocol (MCP) that connects Cursor to the OpenRouter API, enabling functionalities for code review and AI chat.

how to use MCP Server - Code Review?

To use the MCP Server, install it via npm and run it from the command line with your OpenRouter API key. You can utilize the ask tool for text prompts and the code_review tool for automated code reviews.

key features of MCP Server - Code Review?

  • Connects to OpenRouter API for access to various large language models.
  • Provides two main functionalities: text prompt responses and automated code review.
  • Integrates with repomix for codebase packaging and analysis.
  • Supports multi-language project detection.
  • Runs as a stdio server compatible with the MCP protocol.

use cases of MCP Server - Code Review?

  1. Performing automated code reviews for software projects.
  2. Generating responses to programming-related queries.
  3. Analyzing codebases in multiple programming languages.

FAQ from MCP Server - Code Review?

  • What programming languages does it support?

The server supports JavaScript, Python, C#, PHP, Java, Ruby, Go, Rust, C++, and Swift.

  • How do I install the MCP Server?

You can install it globally or locally using npm: npm install -g mcp-server-code-review or npm install mcp-server-code-review.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
arahisman
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago