mcp-repo-context
Extracts PR review comments and source code from GitHub repositories for semantic search.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-repo-contextfind similar review comments about error handling"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-transformersmodule (runs locally, no API keys)Serves 6 MCP tools that Claude Code agents can call during peer reviews and solution planning
Related MCP server: Tea Rags MCP
MCP Tools
Tool | Description |
| Semantic search across past PR review comments |
| Find review feedback related to a specific file |
| All review comments for a specific ticket |
| Semantic search across source code chunks |
| Get all functions/classes in a file |
| List all code in a module |
Prerequisites
Weaviate running with the
text2vec-transformersmodule enabled and reachable atWEAVIATE_HOST:WEAVIATE_PORT(defaults:localhost:8080HTTP,localhost:50052gRPC). Any deployment works — a standalonedocker composestack, a hosted instance, etc.Python 3 with
pip(needsweaviate-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.shOption B: Ingest pre-built JSONL first, then register
cd /path/to/your-repo
/path/to/mcp-repo-context/setup.sh --data-dir ./dataThe --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 --extractThis 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 |
|
| Weaviate HTTP port |
|
| Weaviate gRPC port |
Extraction (when using --extract)
Variable | Default | Description |
| Auto-detected via | GitHub repo in |
| All humans (bots excluded) | Comma-separated GitHub usernames to include |
|
| Regex to extract ticket IDs from PR titles |
|
| JSON array of |
|
| Comma-separated directories to skip |
How it works
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'stext2vec-transformersmodule, so no embeddings live in the JSONL.Extraction is optional. The repo ships with
extract-review-comments.pyandextract-codebase.pyfor generating JSONL from scratch, but you can also hand-author JSONL files if you already have the data.The MCP server runs on the host.
setup.shrunsnpm install && npm run buildagainstmcp-server/and registers the compiledbuild/index.jswith Claude Code viaclaude mcp add. No Docker is required for the server itself.Queries go through a Python bridge. The Node MCP server spawns
query-review-knowledge.py/query-codebase.pyviaexecFile, 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_overviewThen restart Claude Code. Verify registration with claude mcp list.
License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BradBissell/mcp-repo-context'
If you have feedback or need assistance with the MCP directory API, please join our Discord server