Wcagc MCP vs Repo Graph — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Wcagc MCP vs Repo Graph
In-depth architectural comparison of the Wcagc MCP and Repo Graph 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
Wcagc MCP
Biology & Bioinformatics · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Repo Graph
Biology & Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Wcagc MCP if you need specialized Biology & Bioinformatics tools running via a local process. Choose Repo Graph 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 Wcagc MCP when:
You need dedicated capabilities in the Biology & Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Deterministic axe-core accessibility scanning (WCAG 2.1 AA, EN 301 549, PDF/UA) through a wcagc account: scan any public URL or PDF, crawl a whole registered site, replay saved multi-step journeys, and read violation trends. Returns structured findings — rule, severity counts and the success criteria involved — so the assistant reasons over real results rather than guessing from markup. Every scan result carries an automated-coverage disclaimer instead of a score or a pass/fail verdict. Hosted at https://mcp.wcagc.com/mcp, or run it locally with npx -y @wcagc/mcp.
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.
Tools & Capabilities Breakdown
Wcagc MCP Tools (7)
scan_url
Scan any public URL, or a registered site for full tracking (Pro+).
check_pdf
Run a PDF/UA-1 structure check on a public PDF.
list_sites
List the account's registered sites.
scan_site
Crawl and scan every reachable page of a registered site.
get_root_causes
Group a run's repeated DOM patterns and return factual element/page blast radius.
run_journey
Replay a saved multi-step journey and check each step.
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).
Wcagc MCP is categorized under Biology & Bioinformatics and uses a local stdio subprocess. In contrast, Repo Graph belongs to Biology & Bioinformatics using local stdio subprocess. Select Wcagc MCP when you need capabilities focused on biology & bioinformatics and Repo Graph when you require tools for biology & bioinformatics.
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
read
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