Repo Graph vs Omophub MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Repo Graph vs Omophub MCP
In-depth architectural comparison of the Repo Graph and Omophub MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Repo Graph
Biology & Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Omophub MCP
Biology & Bioinformatics · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Repo Graph if you need specialized Biology & Bioinformatics tools running via a local process. Choose Omophub MCP if your workspace requires Biology & Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Repo Graph when:
You need dedicated capabilities in the Biology & Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
The first call on a repo: node/edge counts, detected kinds, entry points, and a **blind-spots** note flagging which languages/edges are under-linked (so you grep those deliberately). `seed=<node>` → scoped map; `full=true` → whole-repo dense map
find
Turn any text into the ranked nodes that matter — a symbol/keyword, or a pasted stacktrace / failing-test id / diff (resolved to the code it implicates). `expand=true` fans out to the surrounding neighbourhood. Every row carries `path:line
impact
Blast radius: what a change affects (`forward`) or depends on / is used by (`backward`), as a ranked, located closure — each row with the edge `via` reason and a `⊘` when the engine finds it unreachable (likely dead). Pass several nodes for a whole-diff radius
trace
One arg: a feature end-to-end across the stack, each hop labelled with its mechanism (call / HTTP / queue / event) and cross-service hops marked. Two args: the shortest path between two nodes
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Repo Graph is categorized under Biology & Bioinformatics and uses a local stdio subprocess. In contrast, Omophub MCP belongs to Biology & Bioinformatics using local stdio subprocess. Select Repo Graph when you need capabilities focused on biology & bioinformatics and Omophub MCP when you require tools for biology & bioinformatics.
A node's exact source, sliced from its file by the graph's line span, plus a `context:` footer (HTTP method, cross-stack callers, covering tests, governing docs). Comma-separate to batch-read a ranked set
refresh
Rebuild the graph (incremental by default — only changed files re-parse). `repo_path` retargets a different path or git URL; `full=true` forces a clean reparse. Routine edits are auto-picked-up by the file watcher
Omophub MCP Tools (11)
search_concepts
Search for medical concepts by name or clinical term across all vocabularies
get_concept
Get detailed info about a specific OMOP concept by `concept_id
get_concept_by_code
Look up a concept using a vocabulary-specific code (e.g., ICD-10 `E11.9`)
map_concept
Map a concept to equivalent concepts in other vocabularies (paginated — see note below)
get_hierarchy
Navigate concept hierarchy - ancestors, descendants, or both
list_vocabularies
List available medical vocabularies with statistics
semantic_search
Search using natural language with neural embeddings (understands clinical meaning)
find_similar_concepts
Find concepts similar to a reference concept, name, or description
explore_concept
Get concept details, hierarchy, and cross-vocabulary mappings in one call
fhir_resolve
Resolve a FHIR coded value (incl. administrative codes via the HL7 FHIR-to-OMOP IG ConceptMaps) to its OMOP standard concept and CDM target table
fhir_resolve_codeable_concept
Resolve a FHIR CodeableConcept — best match by OHDSI vocabulary preference, honoring `userSelected
Structural graph map of any codebase for AI coding assistants. Scans entities, relationships, and feature flows across 13 languages so LLMs navigate by structure instead of grepping through everything.
Search, lookup, map, and navigate OMOP medical vocabularies via AI agents