ragflow-mcp-server-fixed
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ragflow-mcp-server-fixedask your configured chat: what's the revenue for Q3?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ragflow-mcp-server-fixed
A fixed RAGFlow MCP server for stdio MCP clients.
It keeps the executable name ragflow-mcp-server, so clients can switch from
the original package by changing only the package source.
What This Fixes
Some RAGFlow deployments return errors from the legacy chat endpoint, for example:
'NoneType' object is not subscriptable
required argument are missing: messagesThis server handles that by:
calling RAGFlow HTTP APIs directly;
parsing stream responses defensively;
falling back to the OpenAI-compatible RAGFlow endpoint when needed;
returning clearer error messages from RAGFlow.
Tools
Tool | Purpose |
| List RAGFlow datasets. |
| Create a chat assistant and session for a dataset. |
| Ask a question in a session returned by |
| Ask a server-configured RAGFlow chat assistant directly. |
| Retrieve matching chunks directly from a dataset. |
For most usage, configure --default-chat-name or --default-chat-id, then use
ask_configured_chat.
Quick Start
{
"command": "uvx",
"args": [
"--from",
"git+https://github.com/FoundZiGu/ragflow-mcp-server-fixed.git@v0.1.2",
"ragflow-mcp-server",
"--api-key",
"ragflow-REPLACE_WITH_YOUR_KEY",
"--base-url",
"http://<RAGFLOW_HOST>:9380",
"--default-chat-name",
"<CHAT_NAME>"
]
}If your MCP client supports environment variables:
{
"command": "uvx",
"args": [
"--from",
"git+https://github.com/FoundZiGu/ragflow-mcp-server-fixed.git@v0.1.2",
"ragflow-mcp-server"
],
"env": {
"RAGFLOW_API_KEY": "ragflow-REPLACE_WITH_YOUR_KEY",
"RAGFLOW_BASE_URL": "http://<RAGFLOW_HOST>:9380",
"RAGFLOW_DEFAULT_CHAT_NAME": "<CHAT_NAME>"
}
}Use chat ID instead of name when possible:
{
"command": "uvx",
"args": [
"--from",
"git+https://github.com/FoundZiGu/ragflow-mcp-server-fixed.git@v0.1.2",
"ragflow-mcp-server",
"--api-key",
"ragflow-REPLACE_WITH_YOUR_KEY",
"--base-url",
"http://<RAGFLOW_HOST>:9380",
"--default-chat-id",
"<CHAT_ID>"
]
}Server Options
Option | Environment variable | Description |
|
| RAGFlow API key. |
|
| RAGFlow base URL. |
|
| Existing RAGFlow chat assistant ID for |
|
| Existing RAGFlow chat assistant name for |
|
| Session name created for the configured chat. |
Local Development
uv run ragflow-mcp-server --helpexport RAGFLOW_API_KEY="ragflow-REPLACE_WITH_YOUR_KEY"
export RAGFLOW_BASE_URL="http://<RAGFLOW_HOST>:9380"
export RAGFLOW_DEFAULT_CHAT_NAME="<CHAT_NAME>"
uv run python tests/smoke_test.pySecurity
Do not commit API keys.
Prefer environment variables for secrets.
Rotate keys that have appeared in logs, screenshots, public issues, or chat transcripts.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/FoundZiGu/ragflow-mcp-server-fixed'
If you have feedback or need assistance with the MCP directory API, please join our Discord server