Skip to main content
Glama
685,510 tools. Updated 2026-10-22 10:37

"Using an MCP client like Windsurf to communicate on Discord" matching MCP tools:

  • Make Vilix automatic. Call this when the user asks "how do I make this automatic", "set this up so it remembers on its own", or right after a first connection when offering setup. Returns a short custom-instructions block the user pastes into THIS tool's personalization / custom-instructions settings so the AI starts calling Vilix (get_context / save_turn) on its own — plus exactly where to paste it. `recommended` is the block matched to the caller's tool; `blocks` lists every supported tool's block (and for headless always-on tools, an enforce-every-turn variant for an always-on rules file). `source` (optional) — the tool label you run in (e.g. "ChatGPT", "Claude", "Cursor", "Codex", "Copilot", "Windsurf"), used to pick the right block; omit to get the generic default. This is an OPT-IN setup you hand to the user — it is not auto-applied; Vilix logs nothing silently.
    ConnectorOAuth
  • Create a shareable Pairoa invite link for the current user. Returns { ref, url, share_text }. ONLY works after the user has claimed an account (claim_account). Otherwise returns AUTH_REQUIRED — guide them to claim first (claiming happens automatically on their first match). The 'share_text' is ready to forward AS-IS — to a Slack/Discord/WeChat group, a tweet, or a DM. Relay it to the user so they can paste it wherever they like; offer the bare 'url' too if they only want the link. Invites carry NO reward and are purely a convenience for word-of-mouth. Don't over-promote or nag. We do not track who the invitee is — only a private count of how many people a link brought in.
    ConnectorOAuth
  • Given a registry wine_id (or, on an authenticated connection, one of the user's bottle_ids), returns wines with the closest taste/style profile from the shared registry, using vector similarity over wine embeddings. Call for "more like this", "what else is like my favourite Barolo", or to seed purchase ideas from a wine the user loves. Only wines that have been embedded are searchable — an empty result does not mean nothing similar exists. Ids must be 24-hex Mongo ids from search_registry or search_bottles — a name or slug is not an id. Returns at most 10.
    ConnectorNo auth
  • Undo `link_account`. The binding is deleted and the key that was minted for this client is revoked, so the client can no longer reach the account. Your own API key is untouched — this disconnects a client, it does not close an account. Do this on any machine that is not yours, and whenever a personal connector URL or a client id may have been seen by somebody else. Calls afterwards fall back to the keyless trial. Safe to call when nothing is linked. Free.
    Connector
    Destructive
    No auth
  • Take an app offline. Its address stops answering and it stops using resources; nothing is deleted and start_app brings it back. Use this to park an app, not to fix one — a crashed container already restarts on its own.
    Connector
    Destructive
    OAuth
  • Create, update or delete client companies (client teams) and their membership. Companies have no unique name — call company-read "list" with client_id first to check whether a client already belongs to a team before creating a new one. "add_member" requires an existing client account (create one with client-write first) and defaults collaborate_on_new_orders/collaborate_on_new_tickets to true, access_invoices to false, and share_existing_subscriptions to false. "update_member" changes only the flags supplied. "remove_member" of the current owner requires new_owner_client_id, unless they are the company's only member. Every ownership change ("create"/"update" with owner_client_id, "remove_member" with new_owner_client_id) decides whose invoices members with access_invoices can see and who manages the team in the portal, and shares the new owner's existing subscriptions with members who collaborate on orders. "delete" permanently deletes the team, its memberships, pipeline cards and SEO reporting data and cannot be undone; former members keep access to orders, tickets and subscriptions they already collaborate on (use "remove_member" first to revoke it) but lose access to the owner's invoices.
    Connector
    Destructive
    OAuth

Matching MCP Servers

Matching MCP Connectors

  • Read-only discovery of AI agents in your Communicate workspace.

  • Discord MCP Pack

  • Point this MCP client at an account you already have, so header-less calls from it stop spending the keyless trial. **This is for clients that cannot set HTTP headers** — Claude.ai custom connectors and ChatGPT apps. If your client *can* set a header, prefer that: it is per-connection, it is not tied to a network address, and it needs no tool call at all. **Only a client with an identity of its own can be linked.** A connector added with the shared URL and no client id is recognised by its IP address and User-Agent, and every user of a hosted connector shares those: they call from their vendor's servers. Linking that would link all of them, so it is refused. Add this server with a personal URL instead — `https://mcp.galleyrender.com/mcp/c/<id>`, with a random `<id>` of your own (https://galleyrender.com/docs/connect makes one) — or send `X-Galley-Client-Id` with at least 128 random bits, then link. Two ways to prove the account is yours. `api_key`, if you have the key to hand. Or `link_code`, the one-time code mailed to the account's own address — call `create_account` with that address to have one sent, and nobody has to paste a key into a chat window. Either way the credential is used once, checked, and dropped: what is stored is the account id and a key minted for this client, which `unlink_account` revokes. **Whoever has the client id acts as the account.** A personal connector URL or a client id header is a credential once linked: keep it like a key, and `unlink_account` when you are done on a machine that is not yours. Free.
    ConnectorNo auth
  • Start an OAuth Connect and get the consent URL to open in a browser. Pass provider (github|google|x|atlassian|microsoft|slack|notion|gitlab|discord|reddit|linear — account-wide, reused everywhere) OR server_url (any MCP server; Rokha runs the MCP auth-spec handshake, grant bound to that server). On approval the token lands in the vault under the returned alias. Requires a logged-in identity.
    ConnectorNo auth
  • Delete one coupon from an app. WRITE, human-gated: a real delete requires an elicitation-capable client; the human sees the exact coupon (code, percent, redemption count) and must click approve. The model cannot confirm on its own, and confirm_used is only consulted for dry_run previews. Clients without elicitation are refused (dry_run still works anywhere). Removes the Stripe coupon object and then the `coupons` row, exactly like the dashboard's delete, so no orphaned Stripe object is left behind. Deleting is permanent and the code becomes reusable afterwards. Set dry_run:true to see exactly which coupon would go (and its redemption count) without touching anything. Use list_coupons first to confirm the code.
    ConnectorNo auth
  • Add, change or remove environment variables of a hosted app or bot. Pass set as a map of NAME to value for the ones to write, and unset as a list of names to remove. Everything not named is left exactly as it is, values included. The response never contains a value, only the names that were written and removed: pass a value in, never expect one back. Saving environment recreates the container, so the app restarts and is offline for about a minute. Removing DISCORD_TOKEN from a Discord bot is refused, because it would take the bot down for good. A changed DISCORD_TOKEN is checked with Discord first and refused if Discord rejects it. The credentials of a bundled one-click database are written by FadeHost and are put back on every save, so they cannot be changed or removed here. Refuses a paused app and a suspended owner. Needs full access to the app, the same as the panel Environment tab.
    Connector
    Destructive
    No 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
  • List the folders in your account, used to group intakes by client or project. Call this before create_folder or before setting folder_id on define_intake, update_intake, or list_intakes — reuse an existing folder for a returning client instead of creating a duplicate. Returns { folders: [{ id, name, sort_order, intake_count, created_at }] }.
    ConnectorAPI key
  • Send a message to your token's holders Sends a message from the token page `id` to its subscribed holders: in-app always, plus whichever of `push`, `email`, `sms`, `telegram`, `discord` and `xmtp` are listed and each holder has turned on. It goes out at once unless `scheduledAt` is set. A sent message cannot be recalled. Only the page's owner or a manager can send; there is nothing to sign. With no holder group and no segment, `telegram`/`discord` also post once in the token's public community room and Discord webhook; with either, they are DMs only. Limits: the Free plan sends 1 per rolling 7 days per token; paid plans have no plan limit, but every token is held to a safety ceiling (3 an hour and 10 a day by default, 1 a day in a token's first week), and both answer 429 with `resetsAt`. Up to 50,000 recipients per send, largest holders first. A new token's first send to more than 500 holders is held for review: it answers 200 with `recipientCount: 0` and goes out once released. `wallet` must be one of the caller's signed-in wallets (it is recorded as the sender), and `channels` must include `inapp`. When the same token id exists on more than one chain, `crownChain` picks the token; without it the message can reach the wrong token's holders or none. Every link and image is screened: links on a blocklist and images not on IPFS or Arweave answer 422. Needs Sign in with Chain Daddy, allowing changes (scope api:write).
    Connector
    Destructive
    No auth
  • Make an app the default for this connection: later calls that pass no `app` argument act on it. Takes an app id from list_apps. The choice is kept on the connection, so it applies to every session using it; pass `app` on a single call instead when you only need one app briefly.
    ConnectorOAuth
  • Send an intake questionnaire to a client by email or SMS. This MESSAGES THE CLIENT. Identify the client by ClientId, or by ClientName plus ClientEmail and/or ClientPhone (omit ClientEmail to force SMS). PractitionerId is optional. Returns the new intake. IntakeQ: POST /intakes/send.
    Connector
    Destructive
    No auth
  • Posts a finished standup note to the chat webhook the user saved on the connect page (Slack, Discord or Google Chat). This one has a side effect: it sends a message other people will see, so only call it on a note the user has agreed to send. The webhook URL is never an argument. If none is saved, the call fails and says how to add one.
    ConnectorOAuth
  • Start connecting one of the user's own social accounts to their SocialClaw workspace. For most providers this returns an authorizeUrl; give it to the user so they sign in with the provider themselves (SocialClaw never sees their password). Telegram and Discord have no sign-in page: Telegram takes the bot token and chat id of a bot the user created and made admin of their channel, and Discord takes a webhook URL the user created for their channel. Only pass values the user gave you for this purpose.
    ConnectorNo auth
  • Propose a new time for a session on behalf of the client — opens the bilateral coordination loop by creating a pending SessionRequest (it does NOT move the session; the org resolves it with booking_resolve_request). Provide requestedScheduledAt as an ISO datetime (must be future, within ~3 months). Gated by the org's session-request flow flag and rate-limited per (client, session). The event records the session's client as the proposer. Use booking_list_requests to track pending requests.
    ConnectorNo auth
  • Read the same per-client advance balances shown in ExpenseBot's Client advances section. Use for questions like 'how much of Acme's advance remains?', 'which client floats are still open?', or 'do I owe a client a refund?'. A negative ledger balance means money remains to refund; a positive balance means the client owes the user. Returns the existing app handoff for Refund leftover or Bill Client. Read-only: never records a refund, creates an invoice, or recomputes the ledger in model prose.
    ConnectorNo auth
  • FREE: Return the self-service purchase, products, sandbox and checkout navigation needed for an autonomous client to buy Horse Truth machine access. Use this tool when you need to know how to pay: x402 per call, a direct credit pack, or the Apify marketplace. Use sandbox_preview instead to see what a result looks like.
    ConnectorNo auth
  • Switch the workspace THIS MCP session works in. Pass exactly one of `workspace_id` or `slug` (find them via `workspace.list`). Takes effect on the very next tool call — no MCP reconnect, no new API key. The switch is scoped to the current MCP session (the response says `scope: session`), or, for a client that sends no MCP session id, to that client (`scope: client`: every conversation of that client on this key moves together). Other sessions using the same API key are not affected, and the key's own workspace stays the default for new sessions. Sequential checkpoint: do not parallelize tool calls across a switch — calls already in flight when the switch commits will run against the previous workspace. Keys created with workspace_locked=true refuse to switch in either scope (they are pinned to their workspace); use a key belonging to the target workspace instead.
    ConnectorAPI key