A
licenseA
qualityB
maintenanceA local-first MCP server that provides a shared Markdown-based memory for AI coding agents, enabling cross-agent context persistence via tools like memory_search and memory_capture.
16
1
MIT
ideahub_mcp
Related Servers
Alternatives to ideahub_mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables users to transform AI conversations into a structured, searchable knowledge base by saving ideas, code snippets, bookmarks, and reminders. It supports persistent storage through Supabase or PostgreSQL and includes webhook integrations for automating workflows with external tools.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets coding agents build and query a persistent knowledge graph of concepts, architecture, and decisions, enabling them to remember across sessions.307 npm729MIT
- AlicenseAqualityCmaintenanceMCP server for long-term agent memory, providing persistent memory, searchable knowledge, and evolving identity for AI agents.53Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA local-first, team-ready MCP server providing durable memory for LLM-based coding workflows with multiple storage backends and fast search.4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that lets coding agents search, retrieve, and add development notes as plain markdown, capturing and sharing knowledge during live coding sessions.1MIT
TDQS
A4.1/5.0
Scored across 14 tools
Disambiguation4/5
The core write paths (capture vs. checkpoint vs. annotate) are explicitly differentiated by durability and target, and read paths (get, related, search, list, dump) differ by input mode and output shape. Remaining friction: link vs. related (write vs. read of the same relation), and register vs. recognize (actor write vs. read) aren't signalled by their names, so an agent must read descriptions to avoid misselection.
Naming Consistency4/5
Nearly all tools are single lowercase words in a consistent style (capture, checkpoint, annotate, promote, archive, link, search, list, dump). Two outliers break the verb pattern: 'related' is an adjective for a lookup, and 'recognize' is a vague verb that actually means 'inspect/list actors' — ideally list_actor/get_actor.
Tool Count5/5
14 tools for a memory-store domain with two resource types (ideas/checkpoints and actors) is well-scoped. Each tool maps to a distinct lifecycle operation (capture, checkpoint, promote, annotate, archive, link, plus query and health/actor utilities), with no obvious filler.
Completeness4/5
Coverage is strong: full idea lifecycle from checkpoint to promotion to archival, note appending, typed linking, multiple retrieval modes, and actor registration/lookup. Gaps are minor but real: no way to edit an idea's content or tags in place, no unarchive/undo for archiving, and no delete — agents must route corrections through annotate.
Maintenance
ActivityMaintained
ResponsivenessNo issues