Dify Knowledge MCP Server
Related Servers
Alternatives to Dify Knowledge MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA Model Context Protocol server that provides Retrieval-Augmented Generation capabilities using Contextual AI, enabling AI interfaces like Cursor IDE and Claude Desktop to query domain-specific knowledge with context-aware responses and source citations.121-
- FlicenseAqualityDmaintenanceA Model Context Protocol server for reading TiDB RAG knowledge base, enabling browsing, searching, and vector search of knowledge entries.4-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides RAG capabilities for markdown documents using Qdrant for vector storage and Ollama for embeddings, enabling semantic search and document ingestion directly from Cursor IDE.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.25-
- AlicenseNot gradedqualityCmaintenanceExposes Dify knowledge base retrieval capabilities via MCP for use in Cursor and other MCP-compatible clients, enabling semantic search and document browsing.MIT
- AlicenseAqualityDmaintenanceA flexible Model Context Protocol server that makes documentation or codebases searchable by AI assistants, allowing users to chat with code or docs by simply pointing to a git repository or folder.117 npm89MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves configuration status, while the other queries a knowledge base. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern with snake_case naming (get_dify_config, query_dify_knowledge). The verbs 'get' and 'query' are appropriate and distinct, maintaining a predictable naming convention throughout.
With only 2 tools, the server feels thin for a knowledge base domain. It lacks essential operations like creating, updating, or deleting knowledge entries, which limits its utility and scope compared to typical MCP servers.
The tool surface is severely incomplete for a knowledge base server. It only allows querying and checking configuration, missing critical CRUD operations (e.g., add, update, delete knowledge) and other lifecycle management tools, which will likely cause agent failures in comprehensive workflows.