max-docs
Related Servers
Alternatives to max-docs
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceExposes ProsodyAI documentation, SDK references, REST API reference (OpenAPI), and curated implementation recipes to AI coding agents via MCP tools and resources.8MIT- AlicenseAqualityDmaintenanceProvides AI assistants with comprehensive, precise BigCommerce developer documentation via 12 MCP tools, including REST endpoints, GraphQL operations, webhooks, OAuth scopes, and code examples.124 npm3MIT
- FlicenseNot gradedqualityDmaintenanceGive your AI agents instant access to Keboola API documentation. Search endpoints, get parameter details, and generate curl examples—all through MCP tools.-
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT
- 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.36 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides LLM-agnostic access to API documentation through MCP and REST endpoints, enabling AI assistants to retrieve, search, and proxy requests to whitelisted APIs across multiple platforms.-
TDQS
Scored across 8 tools
Each tool targets a distinct documentation aspect: endpoints, guides, bridge API, components, code examples, and general search. No two tools overlap in purpose; even get_bridge_api and get_component use parameters to switch between overview and detail, avoiding duplicate tools.
All tool names follow a consistent verb_noun snake_case pattern: list_endpoints, get_endpoint, search_docs, list_guides, get_guide, get_bridge_api, get_component, get_code_example. The verbs 'list', 'get', and 'search' are used predictably according to the action.
8 tools is well-scoped for a documentation server. Each tool covers a necessary function without redundancy, providing a comprehensive but manageable set for users to explore MAX documentation.
The server covers the full lifecycle of documentation access: listing endpoints, retrieving endpoint details, searching across all docs, listing guides, retrieving guides, accessing Bridge API docs, component docs, and code examples. No obvious gaps exist for the stated purpose.