Side-by-Side Model Context Protocol Comparison
Health Export Mcp vs Codebase Memory Mcp
In-depth architectural comparison of the Health Export Mcp and Codebase Memory 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
Health Export Mcp
Developer Tools · Local stdio
Quality: 31/100 (Emerging) | Auth: No auth required
Codebase Memory Mcp
Developer Tools · Local stdio
Quality: 69/100 (Good) | Auth: No auth required
Verdict Summary: Choose Health Export Mcp if you need specialized Developer Tools tools running via a local process. Choose Codebase Memory Mcp if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Health Export Mcp when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
Choose Codebase Memory Mcp when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: index_repository, list_projects, delete_project.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Health Export Mcp Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Codebase Memory Mcp Tools (14)
index_repository
Index a repository into the graph. Auto-sync keeps it fresh after that.
list_projects
List all indexed projects with node/edge counts.
delete_project
Remove a project and all its graph data.
index_status
Check indexing status of a project.
search_graph
Structured search by label, name pattern, file pattern, degree filters. Pagination via limit/offset.
trace_path
BFS traversal — who calls a function and what it calls (alias: `trace_call_path`). Depth 1-5.
detect_changes
Map git diff to affected symbols + blast radius with risk classification.
query_graph
Execute Cypher-like graph queries (read-only).
get_graph_schema
Node/edge counts, relationship patterns, property definitions per label. Run this first.
get_code_snippet
Read source code for a function by qualified name.
get_architecture
Codebase overview: languages, packages, routes, hotspots, clusters, ADR.
search_code
Grep-like text search within indexed project files.
+2 more tools listed on main page
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).
Health Export Mcp Configuration
Codebase Memory Mcp Configuration
Frequently Asked Questions
More alternatives to Health Export McpMore alternatives to Codebase Memory McpDeveloper Tools category hubCanonical compare URL