apic-docs-mcp
Related Servers
Alternatives to apic-docs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceFastMCP server that lets agents search and fetch IBM i documentation via IBM Documentation's public APIs.2MIT
- FlicenseAqualityDmaintenanceAn unofficial MCP server that exposes public FedRAMP 20x documentation as deterministic, citable lookup tools for AI assistants, with every response citing the exact upstream source.7-
- AlicenseAqualityCmaintenanceA high-performance MCP server providing up-to-date documentation for Go, npm, Python, Rust, Docker, Kubernetes, Terraform, and more — fetched from official sources, not training data.183MIT
- AlicenseAqualityDmaintenanceAn MCP server that serves documentation and enables AI-powered search, Q\&A, and document analysis for developer tools and guides.54MIT
- AlicenseAqualityAmaintenanceMCP server providing a searchable knowledge base for the AT Protocol ecosystem, including protocol docs, lexicons, Bluesky API docs, and cookbook examples.89MIT
- FlicenseAqualityCmaintenanceA read-only MCP server that exposes Automeli's public API documentation (v2 canonical, v1 frozen) to LLMs via fetch and cache over www.automeli.com artifacts. It enables listing, searching, and retrieving endpoints, OpenAPI specs, error explanations, code snippets, and end-to-end flow guides.7-
TDQS
Scored across 3 tools
Each tool has a clear, non-overlapping purpose: searching documentation, reading a specific page, and retrieving the table of contents. An agent can easily select the right tool based on the task.
All tool names follow a consistent verb_noun pattern: search_, read_, get_. There is a minor inconsistency between 'apic_docs' and 'apic_doc' (plural vs singular), but this does not create confusion.
Three tools is a focused, well-scoped set for a documentation server. Each tool serves a distinct and necessary function without redundancy or bloat.
The toolkit covers the full documentation workflow: discovering topics via search, navigating structure via TOC, and retrieving full content via read. There are no obvious gaps for a docs-only MCP server.