Skip to main content
Glama
650,545 tools. Updated 2026-10-14 08:20

"How to connect through SSL" matching MCP tools:

  • Returns the prepaid spending balance of the connected PikaSim agent wallet, in USD. Read-only; makes no changes. Call this before purchase_esim or purchase_phone_plan to confirm sufficient funds, or any time you need the current balance. Requires a connected agent wallet (OAuth or ak_live_ key). If no wallet is connected, the result explains how to connect one.
    ConnectorNo auth
  • Read one file attached to a wiki page — its bytes, base64-encoded — identifying the page by 'pageId' or by 'spaceKey' + 'title' and the file by 'filename' as get_wiki_page lists it. This is how a file is copied from one page to another: read it here, write it with add_wiki_attachment. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; for anything larger — or for putting the file on disk — the pm-files MCP server saves it to a path instead (local_files_setup says how to connect it). Reading needs only permission to see the page.
    ConnectorNo auth
  • Create and route a subdomain of a site-linked domain. Creates the DNS A record (if absent) pointing at the site's server, then configures the nginx vhost and SSL certificate on that server. The domain must already be linked to a site (see link_domain). Idempotent: if the DNS record already exists and points at the site's server, the nginx/SSL steps are (re)applied — safe to re-call, e.g. to retry SSL after DNS propagation. May take up to 3 minutes when a certificate is issued. Requires: API key with write scope. Args: domain_name: Registrable domain linked to a site (e.g. "example.com") subdomain: Subdomain label only, no dots (e.g. "blog") Returns: {"fqdn": "blog.example.com", "domain": "example.com", "site": "my-site", "message": "..."} Errors: NOT_FOUND: Domain not found VALIDATION_ERROR: Domain not linked to a site, invalid label, or an existing record points at a different server
    ConnectorNo auth
  • Connect this conversation to the person's Dreambooth Studio account. The answer's status says what happened. already_connected: an account is connected; nothing to do. awaiting_approval: it returns a link the person opens in their own browser to sign in with Google and approve. A Google account with the same email as an existing Dreambooth account connects that account. Ask them to open it and say when they are done; do not call this tool again while waiting. use_client_sign_in: this client connects accounts through its own app or connector settings, where they can sign in with an email and password or with Google, so no link is returned. Ask them to connect Dreambooth there (the client also asks by itself when a tool needs an account), then repeat their question. Either way, someone who has no Dreambooth account yet gets one when they sign in. Call this when another tool reports that no account is connected, or when someone asks to connect or switch accounts.
    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
  • <summary>Read a Campaign Flow node's "went through" history: prospects who held a position on `node_id` and have since advanced off it, newest visit first — the same per-node History list the Flow node-detail panel renders on node-click. Use it to answer "who passed through the connect step", "who has already been through step 2", or to see where a node's past occupants moved on to. This is the history counterpart to get_campaign_flow's live `current` occupancy count; for who rests on a node *now*, filter query_prospects on `current_node_id` instead. Pass any of the user's campaigns; not limited to the agent in context. Reads the append-only position log directly, so an `off_sequence` node id a later flow edit dropped still returns its history. A node no one has moved off — including the start node, which stores no position rows of its own — comes back empty.</summary> <returns> <description>Dict with node_id, count, and prospects array. `count` is how many prospects went through and moved on in total (independent of `limit`/`offset`, so the page count is ceil(count / limit)); `prospects` is the requested page, newest visit first, each {id, name, email, linkedin_url, provider_id, current_node_id, visited_at} — `current_node_id` is the node they rest on now, `visited_at` the ISO time they last held `node_id`.</description> </returns>
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.
    12
    11 npm
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables users to describe workouts in plain English and have them created as structured Garmin Connect workouts with pace, HR, power, cadence targets, and repeat blocks. Also provides full workout lifecycle management including listing, updating, deleting, and scheduling to the calendar.
    8
    56 npm
    MIT

Matching MCP Connectors

  • Inspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions.

  • MCP server for agent identity and reputation: resolve social handles to wallet addresses, score onchain reputation and send USDC from any MCP client.

  • Attach a file to an issue: pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Attaching a filename the issue already has replaces that file rather than adding a second copy, so retrying this call cannot double it. A file on the person's own disk — a screenshot, a PDF — is better attached by path through the pm-files MCP server than typed out as base64; local_files_setup says how to connect it. Returns the attachment's download URL. Requires permission to edit issues in that project.
    ConnectorNo auth
  • The signed-in Epsilon account behind this session: account id, handle, linked wallets (embedded first), the scopes this client was granted, and which client is connected. Call it first after sign-in to learn the wallet address other tools need. Requires an OAuth session (connect to /mcp/account); on the keyless /mcp endpoint it explains how to sign in instead.
    ConnectorAPI key
  • Connect a WordPress site to XeoRank. Just pass the domain (https:// and www are stripped for you). Returns `onboard_url` — PRESENT THAT TO THE USER AS A CLICKABLE LINK and stop there. That one page walks them through installing the connector plugin, opens their wp-admin, and completes the connection automatically — there is NO Application Password to copy and NO follow-up tool call needed. Poll list_wordpress_sites (or verify_wordpress) to confirm it flipped to verified. Pass transport='ssh' only as a Hostinger fallback.
    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
  • How an AI agent gets access to The Continental: the free Porch pass (no human needed: hashcash + Ed25519), and membership through an operator (price, limits, the three steps they take, the text to forward to them). Also how to configure this server once you have a key. Call this first if you have no key.
    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
  • Use this when the person has no account or key yet, or asks how to connect an agent. Takes no input. Returns the sign-up link, what test and live keys are, how this MCP server is reached and signed in to, and the links to the docs and the OpenAPI document. Do not use this to check a key the person already has: any tool that works with cases says so when its key is missing or refused. No key needed.
    ConnectorNo auth
  • Enable or disable Cloudflare CDN proxy for a site. When enabled (orange cloud): traffic goes through Cloudflare's CDN, gets caching, DDoS protection, and SSL termination at the edge. When disabled (grey cloud): traffic goes directly to origin server. Requires: API key with write scope. Args: slug: Site identifier proxied: true to enable CDN proxy, false to disable Returns: {"domain": "my-site.borealhost.ai", "proxied": true, "ip": "1.2.3.4"}
    ConnectorNo auth
  • Add a custom domain to a sota.io project. Each project supports up to 5 custom domains with automatic HTTPS via Let's Encrypt. Returns DNS setup instructions: for apex domains (example.com), add an A record pointing to 23.88.45.28; for subdomains (app.example.com), add a CNAME record pointing to {slug}.sota.io. Domain statuses: pending (waiting for DNS) → verified (SSL provisioning) → active (live with HTTPS). After DNS is configured, verification and SSL provisioning happen automatically.
    ConnectorNo auth
  • <summary>Generate a URL the user can click to connect a tool. Include the URL in your message as a clickable link. If the user says a service is already connected, call `get_integration_status` first — the service may already be active and need no link. A link that opens fine but whose *connection* then fails is not a link problem — a fresh link routes to the same connect flow and fails the same way. Mint one fresh link and have the user retry once; if it still doesn't connect, the connection is stuck (not a link issue) — call `escalate_to_team` with the integration and what the user tried rather than re-minting again. For linkedin, gmail, and outlook the return also includes `data_backfill` — a sentence stating how far back Sliq syncs history once connected. Relay it with the link so the user knows older data won't appear and how to request a longer backfill; when sharing several connect links in one message, merge the notes into a single short disclaimer instead of repeating one per link.</summary> <returns> <description>Dict with the connect URL, integration name, the `data_backfill` note (linkedin/gmail/outlook), and `connect_note` (linkedin)</description> </returns>
    ConnectorOAuth
  • Connect a generic IMAP/SMTP mailbox directly from the conversation with the mailbox credentials (alternative to the account_connect browser link, which is preferred when the user does not want to type a password in the chat). Nilyo forwards the credentials once to the connection service and never stores them. Start with user + password only (servers are auto-detected); if the result says the IMAP or SMTP configuration is invalid, ask the user for the servers (e.g. OVH: imap ssl0.ovh.net:993 ssl, smtp ssl0.ovh.net:465 ssl; Gmail/Microsoft mailboxes should use the Google/Outlook connection instead). Use account_id to re-authenticate an existing disconnected IMAP account.
    ConnectorOAuth
  • Answer a question ABOUT CAPABLE ITSELF — how-to, setup, or troubleshooting (e.g. 'how do I connect my assistant', 'why didn't this email become a contact', 'what can each role do', 'how do I build a report'). Searches Capable's curated, hand-verified help knowledge base and returns the matching articles verbatim, each with SOURCE citations. This is NOT for the user's CRM data (use get_context / search_records for that). GROUNDING RULE — answer ONLY from the returned articles and cite the article title; do NOT add product behavior from memory. If `confident` is false or no returned article actually answers the question, tell the user you don't have a verified answer and point them to hello@capable.run (email is the BACKUP — remind them that asking here is much quicker). Never guess how Capable works. When an article lists `related` topics you may offer them as follow-ups; pass `article_key` to fetch one specific article. When to use: When the user asks how Capable ITSELF works — setup, how-to, or troubleshooting ('how do I connect my assistant', 'why didn't this email become a contact', 'what can each role do'). Searches Capable's curated, verified help articles and returns them WITH source citations. NOT for the user's CRM data (use get_context / search_records). Answer only from what it returns; if it's not confident, tell the user and point them to support rather than guessing. Example: How do I set up a booking link in Capable?
    ConnectorAPI key
  • Returns the full relationship graph for a given Lexicon term. Each related term includes: the related term's slug and title, a plain-English description of the relationship, a direction (inbound or outbound), and a canonical URL. Read-only. No LLM calls. Use this when you need to understand how terms connect — use lookup_term instead when you need a definition.
    ConnectorNo auth
  • Connect Yandex Metrika to a site. IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the platform can do that step for the user. The tool returns a link — show it and ask them to open it and grant access. Do not poll in a loop: the person may walk away for an hour. Check later through this same tool without the `branch` argument, or through `site_analytics`.
    ConnectorOAuth
  • 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