vector-knowledge-graph-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_nodeC | Add a node to the knowledge graph with properties, embeddings, and metadata. |
| add_edgeC | Create a directed edge between two nodes with relationship type and weight. |
| semantic_node_searchC | Search for nodes using semantic similarity matching against stored embeddings. |
| trace_compliance_chainC | Trace the compliance chain from a requirement through controls to evidence. |
| find_gapsC | Find gaps in the knowledge graph where expected relationships or nodes are missing. |
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 5 tools
Each tool has a distinct purpose: adding nodes, adding edges, semantic search, gap analysis, and compliance tracing. No two tools overlap in functionality.
All tool names use snake_case, but the verb pattern is not entirely uniform: add_node and add_edge follow verb_noun, while semantic_node_search and trace_compliance_chain are less consistent. Still, the naming is clear and predictable overall.
Five tools is an appropriate scope for a knowledge graph server, covering creation, search, analysis, and domain-specific traversal without being overwhelming or too sparse.
The set covers core operations (add, search, analyze) and domain-specific needs (compliance tracing), but missing update and delete operations for nodes and edges, which are common in knowledge graph management.