GraphRAG 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 |
|---|---|
| rag_MLC | |
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 1 tool
Only one tool exists, so there is no possibility of overlap or confusion. The tool's purpose is clear from its description.
With a single tool, naming consistency is trivially maintained. However, the name 'rag_ML' is somewhat cryptic and does not clearly convey its function, so a small deduction is applied.
The server exposes only one tool, which feels insufficient for a GraphRAG MCP. Typical RAG servers offer at least multiple query modes or additional operations, making this count on the low side.
The tool surface is severely incomplete for a RAG system. It only provides a single query function with no capabilities for data ingestion, document management, or configuration, leaving major gaps in expected functionality.