Code-review MCP: review a GitLab MR or GitHub PR against the whole codebase, not just the diff.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"myopic": {
"command": "myopic"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The code-review MCP with the most ironic name in the registry. It's anything but nearsighted — it reviews your merge request against the whole codebase, not
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'myopic' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked myopic against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCP Security Weekly
Get CVE alerts and security updates for io.github.SurajKGoyal/myopic and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The code-review MCP with the most ironic name in the registry. It's anything but nearsighted — it reviews your merge request against the whole codebase, not just the diff in front of it.
Building in public. Reviews GitLab merge requests and GitHub pull requests — pass either URL. Reads the change, reviews it against the whole codebase, and can post the review back as inline comments. Issues and PRs welcome.
The bugs that matter rarely live in the diff. They live in what it doesn't show: the caller three files away that now breaks, the convention every sibling file follows that this one quietly drops, the helper that already exists so this new one is a duplicate. A reviewer that only reads the patch is myopic.
myopic is an open-source MCP server that gives the AI client you already use (Claude, Cursor, …) the structured context to review like someone who knows the codebase. It runs on your machine — your code never leaves it, there's no per-PR bill, and the review happens in your own agent with your own standards:
It pairs with amnesic, my MCP server that gives AI persistent memory of SQL databases.
Everything below works today unless marked planned.
Read the merge request (token-safe by construction):
| Tool | What it does |
|---|---|
mr_review_status | MR metadata + every discussion thread + resolved/unresolved, in one call |
mr_changed_files | a content-free manifest of changed files (paths, stats, noise flags) — no diff content, so it stays small even on a huge MR |
mr_diff_sections | the diff grouped by function/class (AST-aware), budget-bounded |
mr_diff_lines | the diff as line-numbered hunks — exact positions for inline comments — budget-bounded |
On a large MR, the diff tools return a bounded page and list the rest under
omitted_files / truncated instead of failing; lockfiles, generated code, and
binaries are listed but not expanded. Fetch the rest with files_filter.
Review against the whole codebase (point at a local clone):
| Tool | What it does |
|---|---|
dependency_impact | everywhere a changed symbol is used — the blast radius (ripgrep + tree-sitter) |
trace_call_chain | the caller/callee graph of a symbol |
mr_review_context | the headline — for each changed symbol: its impact (always), plus semantically similar code when the optional layer is enabled |
Semantic layer (built in — needs Ollama) — index_repo, code_search,
and the semantic half of mr_review_context. See below.
Close the loop — verify, and (on request) comment:
| Tool | What it does |
|---|---|
mr_verify_review | for each existing review thread, the diff changes near the commented li |