RAGFlow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAGFLOW_API_KEY | Yes | API key for the RAGFlow API server. | |
| RAGFLOW_BASE_URL | Yes | The base URL for the RAGFlow API (e.g., http://172.16.33.66:8060). |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_datasetsB | 列出 RAGFlow 中的所有数据集 |
| retrieveC | 从RAGFlow中指定的数据集检索相关内容 |
| create_chatC | 创建一个新的聊天助手,基于指定的数据集 |
| chatC | 向聊天助手提问 |
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 4 tools
The tools are mostly distinct with clear purposes: chat for queries, create_chat for new assistants, list_datasets for enumeration, and retrieve for content retrieval. However, chat and retrieve could potentially be confused since both involve interacting with datasets, though their descriptions clarify different intents (general Q&A vs. specific content fetching).
All tool names follow a consistent verb-based pattern: chat, create_chat, list_datasets, and retrieve. They use simple, clear verbs without mixing conventions like camelCase or snake_case, making the naming predictable and easy to understand.
With 4 tools, the count is reasonable for a RAG-focused server, covering core operations like chatting, dataset management, and retrieval. It's slightly lean but functional; adding tools for updating or deleting datasets could enhance completeness without being necessary for basic use.
The tools cover key RAG workflows: dataset listing, retrieval, and chat interactions. However, there are notable gaps, such as no tools for creating, updating, or deleting datasets, which limits full lifecycle management. Agents can work around this by focusing on existing datasets, but the surface is incomplete for comprehensive dataset control.