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.45 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search, read, and traverse documentation bundles in Open Knowledge Format via MCP tools.705 npm75MIT

@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.37 npmMIT
- 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
The set splits cleanly into three resource families (api, examples, docs), each with search/read-style operations, so most tools are easy to tell apart. The main soft spot is bharosa_api_search vs bharosa_docs_search, since API reference pages are arguably also bundled docs; the descriptions clarify the difference (API operations vs general doc index) but an agent could still hesitate.
All tools share a predictable bharosa_<resource>_<action> pattern with snake_case throughout. The only deviation is bharosa_api_details, which uses a noun ('details') instead of a verb like read/get, breaking the otherwise uniform verb convention.
Seven tools is well-scoped for a read-only documentation server, with each tool earning its place across three resource families. Nothing feels padded or missing at the count level.
Docs have list/search/read, examples have search/read, and API operations have search/details, covering the core read-only lifecycle. Minor gaps: there is no way to enumerate API operations or list examples directly (only search), so discovery depends on guessing good queries.