Knowledge Forest MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_FOREST_FILE | No | Path to the Knowledge Forest JSON file. Defaults to ~/.knowledge-forest/knowledge-forest.json. Can also be set via the --data-file command-line argument. | ~/.knowledge-forest/knowledge-forest.json |
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| forest_overviewA | Read goals, mastery counts, and the next ready knowledge nodes. Call this first; it never modifies learning state. |
| search_knowledgeA | Search canonical nodes before creating a goal tree. Results include reuse context and current mastery state. |
| get_node_contextA | Read a knowledge node, its goal memberships, prerequisites, dependents, learning entries, verification history, and deterministic diagnosis. |
| create_goal_treeA | Persist one observable goal, its branches, and prerequisite-linked knowledge nodes. Search first. Use reuse_node_id only for truly equivalent existing concepts. |
| update_node_learning_stateA | Set a learner-selected depth or non-verified workflow state. This tool cannot mark mastery; use record_verification for that. |
| append_learning_noteA | Append a note, reflection, source, or exercise to a node. Source-visible material never changes mastery state. |
| record_verificationA | Record one verification attempt. Mastery advances only for demonstrated, novel, unassisted, closed-book performance; the server computes acceptance. |
| get_learning_queueB | Return ready and prerequisite-blocked nodes, ordered by readiness and importance. |
| diagnose_nodeA | Deterministically identify prerequisite, depth, and evidence gaps and recommend the next learning action. It does not call a model. |
| export_forestA | Read the complete portable forest state, including append-only learning records and evidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_learning_goal | Guide the connected model to turn one outcome into a reusable, prerequisite-aware goal tree. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Tools are intentionally separated by task, and descriptions carefully disambiguate state-changing actions, e.g. update_node_learning_state cannot mark mastery and record_verification is the only mastery mechanism. Minor overlap remains between forest_overview and get_learning_queue, and get_node_context already includes diagnosis alongside the dedicated diagnose_node tool, so an agent could occasionally pause between them.
The naming convention is strongly consistent: snake_case verb_noun pairs such as search_knowledge, create_goal_tree, record_verification, diagnose_node, and export_forest dominate the set. forest_overview is the only outlier as a noun_noun name and does not follow the imperative verb pattern used elsewhere, which keeps this from a perfect score.
Ten tools map cleanly to the full knowledge-forest workflow: orient, search, create, update learning state, append evidence, verify mastery, queue readiness, diagnose, and export. The count is well within the ideal range, with no redundant utilities or token bloat relative to the server's purpose.
The set covers the full learning lifecycle for its stated domain: creating goal trees, reading node context, updating non-verified workflow state, appending source-visible notes, recording verification attempts, queueing ready work, diagnosing gaps, and exporting complete portable state. Missing delete or goal-tree editing operations are not obvious gaps because the design is explicitly append-only and evidence-focused, and the tools explicitly prevent dead ends between state mutations.