mcp-lightrag
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIGHTRAG_HOST | No | LightRAG API host | localhost |
| LIGHTRAG_PORT | No | LightRAG API port | 9621 |
| LIGHTRAG_API_KEY | No | Optional API key for LightRAG |
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 |
|---|---|
| query_knowledge_graphB | Search the knowledge graph for information using various strategies. Ideal for answering questions based on indexed data. |
| ingest_textA | Index raw text content directly into the knowledge graph. Useful for small snippets or dynamic data. |
| ingest_fileB | Index a specific local file from the file system. The file must be accessible by the running server. |
| upload_and_indexB | Upload a file to the LightRAG server's input directory and trigger indexing. Handles file transfer if the server is remote. |
| upsert_documentA | Intelligently upload a document: if it doesn't exist, creates it; if it exists and is identical (same content length), skips upload; if it exists but was modified, deletes the old version and re-uploads. |
| ingest_batchB | Recursively index all files in a directory that match specific patterns. |
| list_all_docsA | List ALL documents currently in the system. WARNING: Can be slow if there are many documents. Use get_latest_documents for better performance. |
| find_documentA | Check if a document exists by its filename or path. Returns a dictionary with detailed status: 'id', 'status' (processed/failed/pending), 'created_at', 'updated_at', 'content_length', 'chunks_count', and 'error_msg' if any. |
| get_latest_documentsA | Get a paginated list of the most recently updated documents. Useful for monitoring ingestion progress. |
| check_indexing_statusA | Check the current status of the document processing pipeline (idle or busy). |
| get_graph_metadataA | Retrieve schema information about the knowledge graph, including available node labels and relationship types. |
| verify_server_healthA | Check if the LightRAG server is reachable and healthy. |
| create_entitiesB | Manually insert specific entities into the knowledge graph. |
| remove_entitiesB | Delete one or more specific entities from the knowledge graph by name. |
| purge_by_documentB | Remove all entities and relationships associated with specific document IDs from the graph. |
| modify_entitiesB | Update the properties (type, description, source_id) of existing entities. |
| connect_entitiesB | Define or update relationships between entities, including edge weights and descriptions. |
| unify_entitiesA | Merge multiple source entities into a single target entity to resolve duplicates or synonyms. |
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 18 tools
Most tools have clearly distinct purposes, especially across document ingestion and entity management. However, some overlapping file-related tools (e.g., ingest_file vs upload_and_index) could cause slight confusion, and multiple document retrieval tools (find_document, get_latest_documents, list_all_docs) have overlapping but distinct use cases.
All tool names follow a consistent verb_noun pattern with underscore separators. The verbs are varied but appropriate for each action, and no mixed styles (e.g., camelCase) are present.
18 tools is a well-scoped number for a knowledge graph server. Each tool serves a specific function in document ingestion, entity management, querying, or monitoring, without unnecessary bloat.
The server covers document CRUD and entity management reasonably well, but lacks direct entity retrieval (only via query) and an explicit tool to delete a document record itself (only purge associated entities). These are notable gaps that may hinder agents in certain workflows.