Hoppscotch Public Docs MCP
Related Servers
Alternatives to Hoppscotch Public Docs MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to search Groq's API documentation using natural language queries through an MCP-compatible interface.MIT
- AlicenseAqualityDmaintenanceEnables managing internal documentation with search and add capabilities, and fetching official documentation from 13+ popular libraries via MCP tools.69MIT
- AlicenseAqualityBmaintenanceExposes OpenAPI/Swagger API documentation as MCP tools, enabling AI agents to search, inspect, and call API endpoints through natural language.511 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables agents to query real-time OpenAPI documentation of backend services, providing tools to list services, endpoints, and schemas via MCP.-
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct access to self-hosted Docmost documentation through tools for listing spaces, searching content, and retrieving pages in Markdown format. It facilitates seamless documentation lookup and content retrieval within MCP-compatible clients.5MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch, index, and perform semantic RAG-based searches on API documentation from various sources. It provides tools for hybrid search and collection management, allowing users to access up-to-date documentation from projects like Gemini and FastMCP.-
TDQS
Scored across 4 tools
The tools mostly target distinct actions: get_document retrieves metadata, search_documentation discovers endpoints by concepts, list_endpoints filters by exact text, and get_endpoint fetches full details. list_endpoints and search_documentation both return endpoint lists, but descriptions give clear guidance on when to use each, so ambiguity is minor.
All tool names follow a consistent verb_noun snake_case pattern: get_document, list_endpoints, search_documentation, get_endpoint. The singular/plural variation reflects whether one or many resources are returned, which is predictable.
Four tools are well-scoped for a read-only public documentation MCP. Each tool has a clear purpose and there is no redundant or trivial tool, making the set appropriately sized.
The surface covers document metadata, endpoint listing, concept search, and full endpoint detail retrieval, which are the core read-only operations. Minor gaps exist, such as no dedicated tool for listing saved response examples or separately browsing folders, but these are largely addressable through existing tools.