Skip to main content
Glama
683,860 tools. Updated 2026-10-21 07:55

"How to connect to a REST API" matching MCP tools:

  • Retrieve reference documentation for the Zaira Guide API and MCP server on demand. Topics: - getting_started — how to connect via MCP or REST, first queries - endpoints — full REST endpoint reference with parameters - mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix - schema — the tool entry schema - errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC) Call with no topic to get an index of available topics. Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content. Examples (topic selection): - "How do I call the REST API?" → {topic: "getting_started"} - "What parameters does /tools accept?" → {topic: "endpoints"} - "What fields are in a tool entry?" → {topic: "schema"} - "What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"} - "Which MCP tool fits my task?" → {topic: "mcp_tools"} Edge cases: - No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once. - Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter. Risk: read-only, closed-world, idempotent — no state change possible.
    ConnectorNo auth
  • Built-in product help — a natural-language "how do I…" question about Fastio returns a grounded, product-aware answer (or a short clarifying question) in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything); the actions themselves are on the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls, in place of guessed endpoints or exploratory calls. Q&A over the user's uploaded files (RAG) is the `ai_manage` tool; `how-to` answers questions about Fastio ITSELF. Costs no credits; needs only an authenticated user (no org needed). action='describe' gives the full action/param reference.
    ConnectorNo auth
  • In-chat Vilix help. Call this when the user asks what Vilix is, how to connect a specific AI tool, how to use Vilix day to day, or about the discount / creator offer — and relay the returned `text` (it's written to be read to the user). The agent is the main onboarding surface, so prefer answering here over sending the user to a website. Returns one topic's short, chat-sized answer with a plain-text `text` you can always read out, plus structured fields a guide-card UI can render: relevant `assets` (connect/demo links), `tools` (connectable tools), and the creator-`offer` state. For "how do I make this automatic" the answer points you at the get_setup_instructions tool — call that for the exact paste-in block. `topic` (optional) — what the user is asking about: "overview" (what Vilix is / how to use it, the default), "connect", "using_daily", "make_it_automatic", or "offer" (the creator discount). Free-form labels are accepted and mapped. `tool` (optional) — the AI tool the question is about (e.g. "ChatGPT", "Cursor"), to scope connect / asset links. `viewed` (optional) — log a downstream interaction with what you surfaced: "asset_viewed" when the user opens a demo link, or "custom_instructions_copied". Omit otherwise.
    ConnectorOAuth
  • For a connected AdCreator merchant: your current plan and price, and exactly what each higher plan adds (more videos, longer video duration) with pricing. Requires your AdCreator connection token. If not connected, it explains how to connect. Read-only.
    ConnectorNo auth
  • For clients that connect with an API key rather than OAuth: exchanges a pairing code from the user's account page for an API key. Destructive: it issues a new key and immediately revokes the account's previous one, so any other client still using the old key stops working. OAuth connections are not affected. The key is returned once and cannot be retrieved later; only a hash of it is stored. It is sent as the `X-API-Key` header on MCP and REST requests. Codes are single-use, expire after 15 minutes, and are invalidated after a few wrong attempts.
    Connector
    Destructive
    No auth
  • Connect to the HenryKnows page the person is watching (turns its light green) and get the session to pass on later calls. Call this first if the person gave you a session code; otherwise it is optional — ask_henry and search_sources connect too.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    . A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{
    2,829 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution

Matching MCP Connectors

  • How many proofs can still be anchored today (UTC day) within the free public quota for the caller's IP address. Hosted chat apps connect from their own servers, so their users share one quota. Callers that send their own API key in the X-API-Key header have no quota.
    ConnectorNo auth
  • See which data and chat integrations this workspace has connected, what each provides, and the Twelfth page where a person can connect or configure it. Use it to answer what is connected or how to connect something. It never starts OAuth or changes a connection; for stored workspace defaults use twelfth_get_preferences.
    ConnectorOAuth
  • Backend, CrudManager, and AjaxStore patterns for Bryntum components. Use this alongside the `bryntum` skill when the user needs to connect a Bryntum product to a backend — loading data from an API, persisting changes, or setting up sync. Trigger on phrases like "connect to a backend", "save data", "load from server", "CrudManager", "AjaxStore", "sync", "REST API", or "database" in a Bryntum project context. Returns the skill's instructions as markdown.
    ConnectorNo auth
  • What the user has connected, and what they could connect. Returns every integration available to this account with `connected` true/false, the accounts behind it, the tools it unlocks, and the URL to connect or manage it. Call this BEFORE telling anyone to connect anything, and before saying a source is unavailable: guessing is how the assistant has told people to connect accounts they already had. An integration missing from the list is not offered to this user at all, so do not suggest it. `suggested` is what is worth connecting next, best first, each with the payoff in the user's terms: use it when asked what would help, and lead with the first one rather than listing the shelf. Connecting is a browser grant: hand the user the URL, never claim to have done it. Each row's `steps` is how to connect it: when someone asks how, walk them through those steps and link `url`, which is that integration's page. Services that are not native integrations (Notion, GitHub, Stripe, Linear and dozens more) are connectors: call list_connectors.
    ConnectorNo auth
  • Connect one of the seven certified exchanges (see setup's exchange list) to your account: creates a webhook and links it to your already-saved credentials for that exchange, the same steps 2-4 the website's setup wizard runs. Safe to call more than once -- if a webhook is already linked, it reports connected:true and creates nothing new. If you have no credentials saved for this exchange yet, returns connect_url instead: open it in a browser to add them, then call connect again with the same exchange (for a paper/testnet exchange you can instead call link with its keys; real-money keys are browser-only). Connecting a real-money (non-paper) exchange requires a live-scoped token; any token can connect a paper/testnet exchange. Requires your Autoview account token.
    ConnectorNo auth
  • Who you are and how posterly is connected. view=identity (default): the authenticated user, API key scopes, workspaces, and onboarding next step. Call this first; if onboarding.completed is false, walk About you, Connect, Brand voice, and First post IN THIS conversation and do not send the user to /onboarding-v2. view=status: hosted MCP server version, latest npm version for local app clients, endpoint and API auth health, and update guidance.
    ConnectorAPI key
  • Get a link the person opens to connect ANOTHER, NOT YET CONNECTED Fortnox company to this connection. This is only for adding a company. It is NOT the page for seeing or managing the existing connection: if the person asks which companies are connected, what the connection may do, how to stop changes, how to remove access, or how to invite a colleague — in Swedish often "min anslutning", "anslutningssidan" or "bjud in" — read get_connected_company and give them its connection_url instead.
    ConnectorAPI key
  • Call apis on site "CodeStringers" (https://www.codestringers.com/_api/mcp). Use this to perform an action on visitor's behalf, for example, query the site's data or book an appointment. Before calling this tool, you should ALWAYS check the rest docs (use "SearchSiteApiDocs" tool) for the specific API you want to call. The mentioned tool will give you instructions how to use the API.', 'NEVER try to guess the API or endpoint, ALWAYS check the docs using "SearchSiteApiDocs" tool. The url param should be taken from the "SearchSiteApiDocs" tool. It usually starts with "https://www.wixapis.com".
    ConnectorNo auth
  • Get the credential setup schema to connect Whop using API key or token credentials. Note: This is an unofficial connector and may change without notice.
    ConnectorNo auth
  • List the signed-in user's saved resorts. Requires a SnowSure user access token (OAuth); without one it returns an authorization-required error telling the agent how to connect.
    ConnectorNo auth
  • [Auth Required] Generate a one-time link for an owner to bind this agent to their account. No invoice or payment required. The owner visits the link to connect.
    ConnectorNo auth
  • START HERE. The ZenSched agent guide: how to Connect (Claude.ai) or use a zsc_ key, then fund → locations → workers → shifts → timesheets. Also covers the suggestion box (feedback_submit).
    ConnectorNo auth
  • List the channels alerts can be sent to: Slack channels, Telegram chats, email address lists, webhooks. Telegram chats connect from the dashboard (Settings, Integrations), not through the API.
    ConnectorNo auth
  • Lists all Mobiscroll Connect REST API endpoints (method, path, summary, auth). Use getConnectEndpointSchema for full parameter/response detail of one endpoint.
    ConnectorNo auth