Practitioner Knowledge MCP
Related Servers
Alternatives to Practitioner Knowledge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with a personal knowledge base stored locally on your computer, supporting semantic search, note reading, and writing through Claude Code or mobile apps.13MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude and other AI agents to persistently store, retrieve, and organize decisions, patterns, and knowledge across sessions, so context survives restarts and compaction.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides Claude with persistent local memory and a structured knowledge graph for tracking project states, task dependencies, and historical context. It enables users to store notes, manage task relationships, and perform time-travel queries to reconstruct past information without relying on cloud services.MIT
- AlicenseNot gradedqualityBmaintenanceProvides Claude Desktop with persistent, structured memory and semantic search via a local SQLite knowledge graph, plus a web UI for visualization and management.MIT
- AlicenseAqualityBmaintenanceEnables a shared persistent knowledge vault for Claude Desktop, allowing notes to be saved, retrieved, searched, updated, and deleted across Chat and Code tabs.511 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.8 npm4MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource or action: get_idea retrieves one, list_ideas filters and lists, search_ideas does ranked full-text search, store/update_idea handle mutations, and framework tools are separate. The overlap between list_ideas and search_ideas is minimal and well-clarified by descriptions.
Seven of eight tools follow a clear verb_noun pattern (get_idea, list_ideas, search_ideas, store_idea, update_idea, get_framework, list_frameworks). The outlier is idea_stats, which uses noun_noun, but the overall convention remains predictable.
Eight tools are well-scoped for a knowledge base covering ideas and frameworks. Core operations—retrieve, list, search, store, update, stat—are all present without redundant tools.
Ideas support create, read, update, search, and stats, but there is no delete operation. However, update_idea can change status (e.g., to archived), so agents can work around permanent deletion; frameworks are read-only, which may be intentional for curated reference content.