bharosa-docs-mcp
Related Servers
Alternatives to bharosa-docs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides MCP tools to list and search OpenAI Agents SDK documentation, enabling LLMs to retrieve documentation topics and content via natural language queries.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.771 npm74MIT

@prosodyai/mcp-docsofficial
AlicenseAqualityBmaintenanceExposes ProsodyAI documentation, SDK references, REST API reference (OpenAPI), and curated implementation recipes to AI coding agents via MCP tools and resources.8MIT- AlicenseAqualityDmaintenanceProvides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables agents to query real-time OpenAPI documentation of backend services, providing tools to list services, endpoints, and schemas via MCP.-
- AlicenseAqualityDmaintenanceProvides read-only tools to search, read, and look up Natural API documentation from an AI agent, enabling documentation lookup without credentials.4MIT
TDQS
Scored across 7 tools
Each tool is explicitly scoped to one artifact type (API operations, source examples, general docs), and the read-only nature is repeatedly stated, which helps avoid confusion with execution tools. The only real overlap is between bharosa_api_search and bharosa_docs_search, since API reference content may also be covered by the general docs index; the descriptions hint at this but don't fully disambiguate which to pick first.
All tools share the bharosa_ prefix and a strict noun_verb pattern grouped by collection (docs_list/search/read, examples_search/read, api_search/details), so the set is highly predictable. The one deviation is bharosa_api_details standing in for the *_read slot, which is slightly inconsistent with examples_read and docs_read.
Seven tools is well-scoped for a bundled, read-only documentation server: three collections each get the minimal list/search/read or search/read pair they need. Nothing looks redundant or padded, and no collection is left without a retrieval path.
The read-only documentation lifecycle (list, search, read) is covered for docs and examples, with search/details for API operations and source examples, so agents rarely hit a dead end. The main gap is the absence of an api_list or operation-enumeration tool, forcing agents to discover operations only via search, and there is no way to browse examples for an operation without a literal query.