Side-by-Side Model Context Protocol Comparison
MCP Curiosity Engine vs Plur
In-depth architectural comparison of the MCP Curiosity Engine and Plur 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
Plur
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Curiosity Engine if you need specialized Knowledge & Memory tools running via a local process. Choose Plur 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).
- Primary tools included: find_dormant_notes, find_orphan_notes, suggest_replay_cycle.
P
Choose Plur 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).
- Primary tools included: plur_learn, plur_learn_batch, plur_recall.
Feature & Specification Comparison
Tools & Capabilities Breakdown
MCP Curiosity Engine Tools (5)
find_dormant_notes
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 Configuration
Plur Configuration