Skip to main content
Glama
634,819 tools. Updated 2026-10-03 21:14

"Documentation for Save API" matching MCP tools:

  • 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
  • Read or search ClearPolicy documentation pages via a sandboxed virtual filesystem (rg, cat, head, tree, ls, etc.). Prefer search-docs for conceptual questions; use this when you need exact page content, keyword/regex matches, or docs structure. Paths are documentation pages (e.g. /guides/reminders.mdx), not the customer organization.
    ConnectorOAuth
  • Search Gonka documentation. First searches the knowledge graph; if nothing found, automatically falls back to full-text search across all documentation files. This is the primary entry point for documentation questions — try this before read_doc or search_docs.
    ConnectorNo auth
  • 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
  • Store or update a secret in the project vault. The value is encrypted with AES-256-GCM and can never be read back. Use this to save API keys for integrations. If the key_name already exists, the value is replaced. For production API keys, the Dashboard Vault tab (dashboard.websitepublisher.ai/vault) is the recommended secure alternative — keys go directly to encrypted storage without passing through the AI conversation.
    Connector
    Destructive
    API key
  • Use this when the user supplies API source code and asks for an OpenAPI or Swagger specification. After authorization, this state-changing action consumes AI credits, creates a generation, and returns OpenAPI JSON; it accepts one source_code file or multiple files entries and can save the result to a Space, where it may be publicly accessible.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • 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
  • Find which documentation SETS exist whose NAME matches a substring (e.g. "python" → Python 3.x, "react" → React). Returns doc SETS, NOT their content — this does NOT look up a function/method/API name. To search inside a doc for an entry like "Array.map" or "fetch", use search_index (slug + query).
    ConnectorNo auth
  • 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
  • CALL THIS FIRST. Provisions an API key for the operator. Returns a pcc_live_* key that must be included as 'Authorization: Bearer <key>' on all subsequent requests. Accepts either email OR walletAddress. The key is shown once — save it. Without it, all other endpoints return 401.
    ConnectorNo auth
  • 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
  • USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.
    ConnectorNo auth
  • Search Redpanda API reference documentation by keyword. Returns up to 20 matching endpoints, schemas, or topics with URL, title, and text excerpts. SCOPING (important for accurate results): - api="all" or omit: Search across ALL APIs at once - useful when unsure which API contains the endpoint - api="admin": Search only cluster management (brokers, partitions, configs, users, maintenance) - api="cloud-controlplane": Search only Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Search only Cloud data operations (topics, ACLs, connectors) - api="http-proxy": Search only HTTP Proxy (produce, consume, offsets over HTTP) - api="schema-registry": Search only Schema Registry (register, retrieve, compatibility) WHEN TO USE WHICH: - User asks "broker endpoints" → api="admin" (brokers are cluster management) - User asks "create topic API" → api="all" (topics exist in admin AND cloud-dataplane) - User asks "Cloud cluster API" → api="cloud-controlplane" - User asks about Redpanda APIs generally → api="all" or omit For general Redpanda questions (not API-specific), use ask_redpanda_question instead.
    ConnectorOAuth
  • 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
  • Search ALL JobMojito documentation. This is the single entry point. One call searches both documentation sources in parallel and returns a merged, source-labeled list — you do not need to choose a source or call a separate tool: • "developer" — developer.jobmojito.com: API reference, request/response schemas, tables, webhooks, code examples, integration guides. • "help" — help.jobmojito.com: recruiter, candidate, and administrator product guides (how the platform behaves for end users). Use this whenever you need to understand how a feature, endpoint, field, or workflow works — including before calling an action tool you're unsure about. Then call `get_documentation(url)` with a returned URL to read the full page.
    ConnectorNo auth
  • 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
  • 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
  • Return the full beacon.host documentation as Markdown (the same text as https://beacon.host/skill.md): the REST API, the beacon CLI, accounts and API keys, claiming sites, password protection, and Workers, which run server-side JavaScript at <slug>.worker.beacon.host for APIs and webhook receivers (GitHub, Stripe), including Hono apps, with no Cloudflare account needed. Read it before building a backend, when the user asks about accounts or limits, or when a task needs something publish_site can't do. Setup for every MCP client: https://beacon.host/mcp
    ConnectorNo auth
  • 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 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