Practitioner Knowledge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_MCP_DB | No | Path to the SQLite database file that stores ideas (defaults to ~/.knowledge-mcp/ideas.db) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_ideaB | Save a new idea to the knowledge base. Returns its id and the stored record. |
| get_ideaC | Return the full record for one idea. |
| update_ideaB | Change one or more fields of an existing idea. Omitted fields stay as they are. Returns the updated record. |
| search_ideasA | Full-text search across titles, domains, problems, insights, assumptions, and tags.
Results are ranked best match first. Each has a snippet: the matching passage with
matched words in [brackets], or the opening of the problem when only the domain or
tags matched; |
| list_ideasA | List ideas, newest first, optionally filtered by domain, tag, or status. |
| idea_statsA | Return the total number of ideas, counts by domain and by status, and the most-used tags. |
| list_frameworksA | List the analytical frameworks available, with each one's name, title, category, and when to use it. |
| get_frameworkA | Return one framework's details and its full Markdown text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.