"API Documentation Resources" matching MCP tools:

• search_documentationA

  Extend MCPA

  Search the Extend documentation. Returns matching pages with URLs — results are pointers, not content: fetch the most relevant with get_documentation. An empty results list means nothing matched; different domain terms (feature names, API field names, product vocabulary) usually do. Always available, no workspace targeting.

  ConnectorOAuth

• http_fetchA

  TeardropA

  Fetch a web page and return its main text content, cleaned of markup. Use to read articles, documentation, and other resources referenced by URL. Blocks private and cloud-metadata addresses and re-validates every redirect hop. Use when: Use when a known URL's content is needed and structured tools cannot answer — e.g. reading a linked document or API docs. For general factual lookup prefer web_search; for token prices prefer get_token_price. Limitations: Read-only GET-style extraction returning cleaned text, not raw HTML or binary content. JS-heavy pages may yield little content; private/internal network targets are deliberately unreachable. Alternatives: web_search, get_token_price

  ConnectorNo auth

• search_api_docsA

  Soracom KnowledgeA

  Search SORACOM API documentation, CLI references, and SAM permissions. Use for exact API endpoints, soracom-cli commands, or SAM permission strings. Use search_soracom_docs for service guides, console how-tos, pricing, or IoT recipes. Use get_document on `#/schema/<Name>` links in results to read full API schema fields.

  ConnectorNo auth

• export_terraformA

  Control PlaneA

  Generate Terraform (HCL) for EXISTING Control Plane resources from a self link. Single resource (`/org/acme/gvc/prod/workload/api`) or bulk by path depth — `/org/acme` exports the whole org, `/org/acme/gvc/prod/workload` exports every workload in a GVC. Set `generateImports` to get ready-to-run `terraform import` commands for adopting the resources into Terraform state, and `includeDependencies` to pull in referenced resources. Secrets are never exported; a ref or dependency closure that includes them is refused. An unsupported kind is rejected with the supported list. For an in-memory manifest, use convert_to_terraform.

  ConnectorOAuth

• search_the_rundown_apiA

  TheRundown Documentation MCPA

  Search across the TheRundown API knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about TheRundown API, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

  ConnectorNo auth

• search-docuwriter-platform-docsA

  docuwriterA

  Use this when the user asks how the DocuWriter.ai platform works or requests its published product instructions. Read-only: searches DocuWriter Platform Docs and returns relevant page excerpts with source URLs. It does not search the user's Spaces or the separate API Docs, and it cannot change documentation.

  ConnectorOAuth

• search_official_docsA

  404.directoryA

  Search current first-party OpenAI, Microsoft Learn, AWS, and Cloudflare documentation in one call. Use this as the default documentation research tool for questions involving any of those providers, especially comparisons or cross-cloud architecture. Select only relevant sources when the provider is known; omit sources to search all four in parallel. Returns each provider result separately with partial-failure reporting and provenance. No account or API key is required.

  ConnectorNo auth

• xtiles_get_docsA

  xTilesA

  Fetch an xTiles guide/documentation document by its `xtiles://guide/...` URI. The same documents are also exposed as MCP resources — use this tool when your client cannot read resources directly. Before generating Markdown for any `*_from_markdown` tool, read `xtiles://guide/markdown/overview` (and `/canvas`, `/collections`, `/blocks`) to get the syntax. `xtiles://guide/markdown/design` holds the colours, styles, layout and tab colours created content takes.

  ConnectorOAuth

• http_fetchA

  teardropA

  Fetch a web page and return its main text content, cleaned of markup. Use to read articles, documentation, and other resources referenced by URL. Blocks private and cloud-metadata addresses and re-validates every redirect hop. Use when: Use when a known URL's content is needed and structured tools cannot answer — e.g. reading a linked document or API docs. For general factual lookup prefer web_search; for token prices prefer get_token_price. Limitations: Read-only GET-style extraction returning cleaned text, not raw HTML or binary content. JS-heavy pages may yield little content; private/internal network targets are deliberately unreachable. Alternatives: web_search, get_token_price

  ConnectorNo auth

• get_startedA

  wallet-trackerA

  How to use CabalSpy: the keyless demo, where to get a free API key (1000 requests, no cost), pricing, documentation, and what the data covers. Call this first if you do not have a key yet, or if another tool returned an auth error or 'demo_limit_reached'.

  ConnectorNo auth

• avizo_docsA

  avizo-mcpA

  Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.

  ConnectorNo auth

• generate-codebase-documentationA

  docuwriterA

  Use this when the user wants a new documentation Space built from selected files in an imported repository. After authorization, this state-changing action consumes AI credits, creates a private Space, links the repository, and queues per-file jobs using repository_id and selected_files.

  ConnectorOAuth

• generate-full-tree-documentationA

  docuwriterA

  Use this when the user has reviewed a full-tree preview and asks to create its documentation Space. After authorization, this state-changing action consumes AI credits, creates a private linked Space, and queues documentation from the stored preview using repository_id and accepted_tree_hash.

  ConnectorOAuth

• compras_listar_resourcesA

  MCP Compras.gov.brA

  Lista os MCP Resources disponíveis com URI, nome e mime-type. Tools de descoberta para clientes que não expõem UI de attachment de resources (como o Claude.ai web). Em Claude Desktop / Cursor / MCP Inspector, resources aparecem em picker dedicado. Resources contêm dados de referência estáticos (tabelas de domínio, glossário, metadados do servidor). Use `compras_obter_resource(uri)` para ler o conteúdo. Retorno: { "total": int, "resources": [ {"uri": str, "nome": str, "descricao": str, "mime_type": str, "tags": [str,...]}, ... ] }

  ConnectorNo auth

• read_contentA

  Evergences — Memos, Content and Shared MemoryA

  Read full public page or API documentation by an exact canonical URL from search_content or resources/list. Never fetches arbitrary URLs.

  ConnectorNo auth

• scalingo_requestA

  Scalingo MCP by usefulapiA

  Power-user escape hatch: GET any Scalingo API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Path is taken after /v1 (e.g. "/apps/my-app/alerts"). By default hits the regional API; set on_auth_host:true for auth-host resources (regions, scm_integrations, tokens). Scalingo API: GET {path}.

  ConnectorNo auth

• design_system-get_filesA

  Anima MCP ServerA

  Fetch multiple documentation files by their paths. Returns a JSON object mapping file paths to their content. Use this after getting the manifest to retrieve specific files like README.md, COMPONENTS.md, TROUBLESHOOTING.md or component documentation.

  ConnectorOAuth

• search-docsA

  ClearPolicyA

  Search ClearPolicy customer documentation for product how-tos, guides, and API reference. Use this for "how do I…" questions (reminders, Planning Center, groups, billing, etc.). Do not use this for organization-specific data — use list/get tools instead.

  ConnectorOAuth

• search_honeydew_documentationA

  Honeydew AI DocumentationA

  Search across the Honeydew Documentation knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Honeydew Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

  ConnectorNo auth

• search_docsA

  mcpA

  Search the Applivery documentation by keyword or phrase. Returns matching pages with title, canonical URL, a highlighted snippet, docType ('guides' or 'api'), platform, breadcrumb and in-page headings. Use this first to discover pages, then read one with get_doc_page. For non-developer questions prefer docType 'guides'.

  ConnectorNo auth

• list_error_codesA

  Trillboards DOOH AdvertisingB

  List every error code in the Trillboards API error catalog. WHEN TO USE: - Understanding what error codes the API can return. - Building a client-side error handler that covers all cases. - Looking up error types, HTTP statuses, and documentation URLs. RETURNS: - object: "list" - data: Array of { code, type, http_status, description, doc_url } - total: Total number of error codes. Equivalent to GET /v1/errors but executed in-process (no HTTP round-trip). EXAMPLE: Agent: "What error codes can the API return?" list_error_codes()

  ConnectorNo auth