A
licenseNot graded
qualityD
maintenanceEnables to search and retrieve chunks from a fictional library's documentation through three tools (kb_search, kb_fetch, kb_sources), allowing LLMs to perform RAG queries via the Model Context Protocol.
MIT
Context11 MCP Server
by vedadsose
Related Servers
Alternatives to Context11 MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access Contractor Scale internal context, including client background, meeting transcripts, and team summaries, via three tools: list_clients, get_client_context, and get_meetings.-
- FlicenseAqualityCmaintenanceEnables AI assistants to search, read, and retrieve context from local knowledge bases with full-text search, absolute paths, and section-level details.4-
- AlicenseAqualityDmaintenanceEnables seamless integration with Convolut Context Bank for AI-powered context management, search, consolidation, and export operations. Provides 11 powerful tools for creating, managing, and analyzing contexts with semantic search and automated planning capabilities.115 npmMIT
- AlicenseAqualityDmaintenanceProvides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.76 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables an agent to read, write, search, and question a PlusGPT knowledge base instance using the caller's own API key, with tools for pages, folders, files, imports, and indexing.-
TDQS
B3.3/5.0
Scored across 6 tools
Disambiguation2/5
The tools get_document and read_document are nearly identical—both retrieve full document content by ID—causing clear ambiguity. Other tools are distinct, but this overlap creates confusion over which to use.
Naming Consistency4/5
Tool names follow a consistent verb_noun pattern (search_, get_, list_, read_, update_). However, the use of both 'get' and 'read' for the same operation is a minor inconsistency that disrupts the pattern.
Tool Count5/5
With 6 tools, the server is well-scoped for a document/knowledge base management purpose. Each tool, apart from the get/read duplication, occupies a clear functional role, and the count is neither sparse nor bloated.
Completeness2/5
The surface covers search, listing, reading, and updating documents, but lacks create and delete operations. This is a significant gap for a document management server, as users cannot add or remove documents through the tools.
Maintenance
ActivityInactive
ResponsivenessNo issues