{ "endpoint": "https://docs.bump.sh/mcp", "captured": "2026-10-20", "method": "initialize + tools/list (anonymous, no tool called; roadmap#992)", "protocol_version": "2025-06-18", "server_info": { "name": "Documentation Portal API", "version": "0.1.0" }, "result": { "tools": [ { "name": "search", "description": "Search across all documentation pages in the portal by keyword. Returns matching pages with their URL, title, type, and a text excerpt. Use this to find specific endpoints, schemas, or topics when the user asks about a particular feature or concept. Supports filtering by object type (api, operation, request, response, property, guide..) 2 outputs are returned: \"data\" returns a maximum of 20 results, and \"total\" returns the total number of results.\n", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "url": { "type": "string", "description": "The base URL of the documentation or hub to search. (e.g., \"https://docs.example.com\"). Default to the portal_url if omitted.\n" }, "query": { "type": "string", "description": "Search query string. Matches against page titles, content, and metadata. Use specific terms for best results (e.g., \"create user\" rather than \"user\").\n" }, "type": { "type": "string", "description": "Filter results by object type. Useful to narrow down results when looking for a specific kind of documentation page. If omitted, all types are returned.\n", "enum": [ "hub", "api", "guide", "group", "operation", "request", "response", "property", "model", "message", "binding" ] } }, "required": [ "query" ] } }, { "name": "get_pages", "description": "Retrieve the full content of one or more documentation pages by their URLs. Returns the full content of the pages, including their titles and types. Use this when you already know which pages you need (e.g., from search results or from list_pages) and want to read their full content. Pass multiple URLs in a single call to batch-fetch several pages at once.\n", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "urls": { "type": "array", "items": { "type": "string" }, "minItems": 1, "maxItems": 10, "description": "List of page URL paths to retrieve (1–10 URLs per call). Use the URLs returned by the search or list_pages flows.\n" } }, "required": [ "urls" ] } }, { "name": "list_pages", "description": "List all child pages under a given URL in the portal hierarchy. Use this to explore and navigate the portal structure. Returns a summary of each child page (URL, title, type and description) without full content. This is the best starting point to understand what documentation is available before fetching specific pages with get_pages.\n", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "url": { "type": "string", "description": "Parent URL to list children of. Default to the portal_url if omitted. Use a hub URL to list every API doc in that hub, or a documentation URL to list every page of that documentation: operations, schemas, topics, etc.\n" } } } }, { "name": "list_changes", "description": "List visible documentation changes for a given resource. Supported resource types are a Hub, an API documentation, or a specific version. Returns changes ordered from most recent to oldest, with pagination support.\n", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "url": { "type": "string", "description": "Target resource URL (hub, API documentation, or version). Default to the portal_url if omitted.\n" }, "page": { "type": "integer", "description": "Changes page number. Default to 1.", "default": 1 }, "limit": { "type": "integer", "description": "Maximum number of changes per page (1–20). Defaults to 20.", "default": 20 } } } }, { "name": "get_change", "description": "Retrieve a single visible documentation change by its identifier. Returns the full change details including title, description, markdown diff content, and creation date. Use this after list_changes to read the full content of a specific change.\n", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "description": "Unique identifier (UUID) of the documentation change. Use the id returned by list_changes.\n" } }, "required": [ "id" ] } } ] } }