MCP Curiosity Engine vs Codebase Memory MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Curiosity Engine vs Codebase Memory MCP
In-depth architectural comparison of the MCP Curiosity Engine 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
MCP Curiosity Engine
Knowledge & Memory · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Codebase Memory MCP
Knowledge & Memory · Local stdio
Quality: 72/100 (Great) | Auth: No auth required
Verdict Summary: Choose MCP Curiosity Engine if you need specialized Knowledge & Memory tools running via a local process. Choose Codebase Memory MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
M
Choose MCP Curiosity Engine when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Surface the notes you forgot you wrote — DMN replay for markdown vaults.
Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp
List notes that are structurally dormant — low incoming wikilink count AND old mtime. These are the notes most at risk of being forgotten.
find_orphan_notes
List notes with zero incoming wikilinks — structurally isolated, the extreme case of dormancy.
suggest_replay_cycle
Run the full DMN-inspired replay cycle: sample dormant notes with bias (40% random / 30% least-linked / 30% orphans), extract their concepts, generate cross-domain bridge queries between them, return notes to revisit. The core moat.
find_cross_domain_bridges
Surface pairs of notes from DIFFERENT top-level directories that share concepts. These are the surprise connections — ideas that span your vault's silos.
random_deep_cut
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).
MCP Curiosity Engine is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Codebase Memory MCP belongs to Knowledge & Memory using local stdio subprocess. Select MCP Curiosity Engine when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.
Pull a single random dormant note for serendipitous rediscovery. Think of it as your vault's shuffle-play button.
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
Structural, BM25, and semantic search. Page structural rows with `offset`/`limit` and ranked semantic rows independently with `semantic_offset`/`semantic_limit`.
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.