Open WebUI Knowledge MCP
Related Servers
Alternatives to Open WebUI Knowledge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables semantic search and knowledge management for local LLM clients through MCP, using locally embedded vectors stored in Qdrant.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes Open WebUI Knowledge Bases as tools and resources, enabling AI assistants to search and access knowledge bases.4MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Open WebUI Knowledge Bases – search and access your knowledge bases from Cursor, Claude Desktop, and other MCP clients.24 npm11MIT
- AlicenseNot gradedqualityDmaintenanceA knowledge base MCP server backed by Qdrant vector database with local embeddings for semantic search and document management.4 npm1ISC
- AlicenseAqualityCmaintenanceEnables indexing and semantic search of codebases and documents via MCP, using Ollama embeddings and Qdrant vector store.5Apache 2.0

fayna-rag-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables local knowledge base management with retrieval-augmented generation (RAG), providing semantic search, document reading, listing, and Q&A via MCP tools and REST endpoints, all running locally without cloud dependencies.MIT
TDQS
Scored across 12 tools
Several tools are exact aliases (rag_get_file/knowledge_get_file, rag_list_knowledge/knowledge_list, rag_search/knowledge_search), so an agent must arbitrarily choose between duplicate entry points. The remaining tools are mostly distinct, but the duplicated surface creates real selection ambiguity.
The knowledge_* tools follow a mostly consistent snake_case verb_noun pattern, but rag_* aliases introduce a second prefix convention. Names like knowledge_get and knowledge_get_file are also close enough to be mildly confusing.
Twelve tools is within a reasonable range, but three are exact aliases padding the count. The effective surface is about nine unique operations, which is well-scoped for this domain.
File operations are well covered with add, get, update, delete, and search, and knowledge bases support list, create, and get. However, knowledge bases lack update and delete operations, leaving an obvious lifecycle gap.