Dify External Knowledge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIFY_API_KEY | Yes | API key for authenticating with the Dify API | |
| DIFY_KNOWLEDGE_ID | Yes | The specific Dify knowledge base ID to query | |
| DIFY_KNOWLEDGE_ENDPOINT | Yes | Dify external knowledge API endpoint URL (e.g., https://your-endpoint.com) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_dify_knowledgeC | Query Dify external knowledge base to retrieve relevant information based on a search query. Returns ranked documents with content, scores, titles, and metadata. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as querying a knowledge base, and no other tools exist to cause confusion.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'query_dify_knowledge' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server that appears to handle external knowledge base operations, as it suggests limited functionality. Typically, such a domain would benefit from additional tools like create, update, or delete operations for knowledge management, making this feel incomplete.
The tool set is severely incomplete for a knowledge base server. While querying is a core function, there are obvious gaps such as tools for adding, updating, deleting, or listing knowledge base entries, which are essential for full lifecycle coverage in this domain.