DOOR Knowledge MCP Server
Related Servers
Alternatives to DOOR Knowledge MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityNot gradedmaintenanceEnables semantic search of project documentation using hybrid vector and full-text search with fast and deep query modes for immediate results or complex multi-round synthesis.MIT- AlicenseNot gradedqualityCmaintenanceEnables LLMs to query documents using semantic search, supporting PDFs, Word, Excel, and more. Organizes documents by topics from folder structure and provides advanced search features like phrase matching and date filtering.1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceCrawls documentation websites and provides semantic search capabilities over the content through vector embeddings, enabling natural language queries of technical documentation.2MIT
- FlicenseBqualityFmaintenanceTransform your non-existent or unreadable docs into an intelligent, searchable knowledge base that actually answers those 'basic questions' before they're asked.1135-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to parse and search documents including PDF, Word, Excel, PowerPoint, and images via OCR, with support for semantic search and batch processing.2MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides comprehensive access to MoEngage documentation from developers, help, and partners portals with full-text search, automatic updates, and intelligent filtering by platform, category, and source.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_door_document retrieves a specific document by ID, list_door_categories lists categories with counts, and search_door_knowledge searches for documents using keywords or categories. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure (get_door_document, list_door_categories, search_door_knowledge). The naming is predictable and enhances readability across the tool set.
With only 3 tools, the server feels thin for a knowledge base domain, as it lacks operations like creating, updating, or deleting documents or categories. While the tools cover basic retrieval and listing, the count is borderline for comprehensive coverage.
The tool surface is significantly incomplete for a knowledge base server. It only supports read operations (get, list, search) with no ability to create, update, or delete documents or categories. This will cause agent failures when full lifecycle management is needed.