Knowledge Graph MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_nodeB | Create a new concept node in the knowledge graph. |
| add_edgeB | Create a relationship between two concepts in the knowledge graph. |
| update_nodeC | Update a node's properties and record a review session. |
| query_graphC | Query the knowledge graph for learning insights. |
| read_subgraphB | Get the neighborhood around a concept for context. |
| get_learning_pathA | Get the ordered learning path to reach a target concept. Returns a topologically sorted list of prerequisites, highlighting which concepts the student still needs to learn (gaps). |
| get_statisticsA | Get summary statistics for learning progress. |
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 7 tools
Each tool targets a distinct operation: adding/updating nodes/edges, querying subgraphs, getting learning paths, and statistics. There is no ambiguity between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_edge, get_learning_path), making them predictable and clear.
With 7 tools, the set is well-scoped for a knowledge graph server covering creation, updates, queries, and analytics without unnecessary bloat.
The set covers core CRUD for nodes and edges but missing delete operations for both nodes and edges, which is a notable gap for lifecycle completeness.