mcp-repo-context

mcp-repo-context

A Weaviate-backed MCP server that gives Claude Code agents semantic search over your repository's PR review comments and source code.

Category
Visit Server

README

mcp-repo-context

A Weaviate-backed MCP server that gives Claude Code agents semantic search over your repository's PR review comments and source code.

What it does

  • Extracts PR review comments from GitHub and chunks your source code into functions/classes/types
  • Embeds everything into Weaviate via the text2vec-transformers module (runs locally, no API keys)
  • Serves 6 MCP tools that Claude Code agents can call during peer reviews and solution planning

MCP Tools

Tool Description
search_similar_reviews Semantic search across past PR review comments
get_review_patterns_for_file Find review feedback related to a specific file
get_ticket_review_history All review comments for a specific ticket
search_codebase Semantic search across source code chunks
get_file_chunks Get all functions/classes in a file
get_module_overview List all code in a module

Prerequisites

  • Weaviate running with the text2vec-transformers module enabled and reachable at WEAVIATE_HOST:WEAVIATE_PORT (defaults: localhost:8080 HTTP, localhost:50052 gRPC). Any deployment works — a standalone docker compose stack, a hosted instance, etc.
  • Python 3 with pip (needs weaviate-client>=4.0.0)
  • Node.js >= 18
  • Claude Code CLI (claude)
  • GitHub CLI (gh), authenticated — only required if you extract fresh review data

Quick Start

The setup script is designed to be run from the root of the repo you want to index. It verifies Weaviate connectivity, optionally ingests data, builds the MCP server, and registers it with Claude Code.

Option A: Register against already-ingested Weaviate

cd /path/to/your-repo
/path/to/mcp-repo-context/setup.sh

Option B: Ingest pre-built JSONL first, then register

cd /path/to/your-repo
/path/to/mcp-repo-context/setup.sh --data-dir ./data

The --data-dir flag points at a directory containing review-comments.jsonl and/or codebase-chunks.jsonl (schema is defined by ingest.py).

Option C: Extract fresh data from GitHub, ingest, then register

cd /path/to/your-repo
REVIEW_AUTHORS=your-github-username /path/to/mcp-repo-context/setup.sh --extract

This runs extract-review-comments.py and extract-codebase.py against the current repo, writes JSONL into ./data/, ingests into Weaviate, and registers the MCP server.

Configuration

All scripts read configuration from environment variables.

Weaviate connection

Variable Default Description
WEAVIATE_HOST localhost Weaviate host
WEAVIATE_PORT 8080 Weaviate HTTP port
WEAVIATE_GRPC_PORT 50052 Weaviate gRPC port

Extraction (when using --extract)

Variable Default Description
GITHUB_REPO Auto-detected via gh GitHub repo in owner/repo format
REVIEW_AUTHORS All humans (bots excluded) Comma-separated GitHub usernames to include
TICKET_PATTERN [A-Z]+-\d+ Regex to extract ticket IDs from PR titles
SOURCE_GLOBS **/*.ts, **/*.vue, **/*.js JSON array of [label, glob] pairs
EXCLUDE_DIRS node_modules,dist,... Comma-separated directories to skip

How it works

  1. Weaviate stores the data. Two collections are created by ingest.py — one for review comments, one for codebase chunks. Vectors are generated at ingest time by Weaviate's text2vec-transformers module, so no embeddings live in the JSONL.
  2. Extraction is optional. The repo ships with extract-review-comments.py and extract-codebase.py for generating JSONL from scratch, but you can also hand-author JSONL files if you already have the data.
  3. The MCP server runs on the host. setup.sh runs npm install && npm run build against mcp-server/ and registers the compiled build/index.js with Claude Code via claude mcp add. No Docker is required for the server itself.
  4. Queries go through a Python bridge. The Node MCP server spawns query-review-knowledge.py / query-codebase.py via execFile, passing JSON args and reading JSON results from stdout. This keeps the Weaviate client in Python while the MCP protocol is served over stdio from Node.

After setup

The setup script registers an MCP server named review-knowledge. To use its tools in Claude Code, allowlist the tool IDs in your Claude Code permissions:

mcp__review-knowledge__search_similar_reviews
mcp__review-knowledge__get_review_patterns_for_file
mcp__review-knowledge__get_ticket_review_history
mcp__review-knowledge__search_codebase
mcp__review-knowledge__get_file_chunks
mcp__review-knowledge__get_module_overview

Then restart Claude Code. Verify registration with claude mcp list.

License

MIT — see LICENSE.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured