Hoppscotch Public Docs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOPPSCOTCH_DOCS_ORIGIN | No | Allowed public viewer origin | https://api-docs.hoppscotch.io |
| HOPPSCOTCH_API_BASE_URL | No | Backend base URL for compatible self-hosted deployments | https://api.hoppscotch.io/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_documentB | Get a published document's title, versions, folders, variables, and endpoint count. |
| list_endpointsB | List endpoints using an exact text fragment, or list all with query="". Paginate for all results. |
| search_documentationA | Start here for broad tasks: rank endpoints by API concepts in a phrase. Returns short summaries and IDs, not full docs. Search focused concepts (e.g. tenant), paginate when the user asks for all, then use get_endpoint for needed routes. This reads documentation, not live API data. |
| get_endpointA | Get full request details for an ID from search_documentation or list_endpoints. Pass response_name for a saved response example. Call only for relevant routes to keep context small. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.