Code Review Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Code Review Server?

The Code Review Server is a custom MCP server designed to perform code reviews using Repomix and Large Language Models (LLMs). It helps developers analyze codebases and provides structured feedback on code quality.

How to use Code Review Server?

To use the Code Review Server, clone the repository, install dependencies, configure your LLM provider in the .env file, and start the server. You can then use the analyze_repo and code_review tools to analyze your codebase.

Key features of Code Review Server?

  • Flatten codebases using Repomix
  • Analyze code with Large Language Models
  • Get structured code reviews with specific issues and recommendations
  • Support for multiple LLM providers (OpenAI, Anthropic, Gemini)
  • Handles chunking for large codebases

Use cases of Code Review Server?

  1. Performing comprehensive code quality assessments.
  2. Identifying security vulnerabilities and performance bottlenecks.
  3. Analyzing codebases for maintainability and best practices.
  4. Flattening codebases for initial analysis.

FAQ from Code Review Server?

  • Can I use any LLM provider?

Yes! The server supports multiple LLM providers including OpenAI, Anthropic, and Gemini.

  • How do I configure the server?

You need to create a .env file based on the provided template and set your preferred LLM provider and API key.

  • What output format does the code review provide?

The code review is returned in a structured JSON format containing a summary, issues, strengths, and recommendations.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago