Skip to main content
Glama
606,759 tools. Updated 2026-09-24 11:22

"Subscribing to Resources and Receiving Notifications" matching MCP tools:

  • Long-poll: blocks until the next edit lands on this board, then returns. WHEN TO CALL THIS: if your MCP client does NOT surface `notifications/resources/updated` events from `resources/subscribe` back to the model (most chat clients do not — they receive the SSE event but don't inject it into your context), this tool is how you 'wait for the human' inside a single turn. Typical flow: you draw / write what you were asked to, then instead of ending your turn you call `wait_for_update(board_id)`. When the human adds, moves, or erases something, the call returns and you refresh with `get_preview` / `get_board` and continue the collaboration. Great for turn-based interactions (games like tic-tac-toe, brainstorming where you respond to each sticky the user drops, sketch-and-feedback loops, etc.). If your client DOES deliver resource notifications natively, prefer `resources/subscribe` — it's cheaper and has no timeout ceiling. BEHAVIOUR: resolves ~3 s after the edit burst settles (same debounce as the push notifications — this is intentional so drags and long strokes collapse into one wake-up). Returns `{ updated: true, timedOut: false }` on a real edit, or `{ updated: false, timedOut: true }` if nothing happened within `timeout_ms`. On timeout, just call it again to keep waiting; chaining calls is cheap. `timeout_ms` is clamped to [1000, 55000]; default 25000 (leaves headroom under typical 60 s proxy timeouts).
    ConnectorNo auth
  • Long-poll subscription that pushes ctx.info() on each new inbox file. Replaces bash polling daemons (watch-relay-*.sh) with server-initiated push. Call once at session start (e.g. via SessionStart hook). Server holds the subscription, watches the calling agent's role-specific inbox dir, and fires info-level notifications on each new relay file arrival. Client re-calls this in a loop for persistent coverage. Per PR #1 (CCR-inversion-for-relay-pickup): `inbox_filter` parameter added to BYPASS role-based dir resolution. Use when role detection is unreliable OR when subscribing to a specific canonical inbox (e.g., 'cc_tb'). Closes 3-week-old feedback_relay_arrival_invisible_midsession HARD RULE.
    ConnectorNo auth
  • Read a connected X/Twitter account's private surfaces: bookmarks and bookmark folders, notifications, and DM history. Billed per item returned; readable only for handles this wallet connected. Guidance: PREREQUISITE: connect an X account (see /api/x-accounts/start). Reads act AS that account, so you can only read the inbox of a handle THIS wallet connected. action=bookmarks (optional folderId) | bookmark_folders | notifications (optional type) | dm_history (target_user_id required). bookmarks/notifications/dm_history are billed per item — set resultsLimit (1–10000). account (the connected handle) is required.
    ConnectorNo auth
  • Use this when the user wants monitoring notifications for a site to go somewhere else, or wants to stop or restart them — routing alerts to a shared inbox, or quietening a site during a rebuild. WRITES to this website's Inclusify configuration, never to the site itself. Three independent settings, all optional: the notification email address, whether regression ALERTS are sent, and whether the periodic DIGEST is sent. Anything you leave out is left exactly as it is, so you can change one without knowing the other two. Pass an empty string for the email to clear the override and fall back to the account's billing address. This REQUIRES CONFIRMATION — call without "confirm" first, show the user the preview, and call again with the token once they agree — because turning alerts off or repointing them is a change that hides its own consequences: the site can regress and nobody hears. The PREVIOUS recipient is emailed a record with a link to undo it, which is deliberate — the person who just stopped receiving these is the one who needs to know. It does not change what is monitored: use add_monitored_pages for that.
    Connector
    Destructive
    API key
  • Pull down the notification panel, the Quick Settings panel, or collapse open panels. action="notifications": pull down the first panel (notifications). action="settings": pull down Quick Settings (some OEMs require notifications first). action="collapse": close any open panel. Tries control channel first; falls back to `cmd statusbar` shell on error. Returns { ok, action, transport }.
    ConnectorOAuth
  • Attach a Stripe payment method to your Disco account. The payment method must be tokenized via Stripe's API first — card details never touch Disco's servers. Required before purchasing credits or subscribing to a paid plan. To tokenize a card, call Stripe's API directly: POST https://api.stripe.com/v1/payment_methods with the stripe_publishable_key from your account info. Args: payment_method_id: Stripe payment method ID (pm_...) from Stripe's API. api_key: Disco API key (disco_...). Optional if DISCOVERY_API_KEY env var is set.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    D
    quality
    D
    maintenance
    Enables MCP agents to send desktop notifications for completed tasks, failures, and important updates, providing visible and reliable feedback.
    1
    39 npm
    2
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables sending real-time and webhook notifications when AI agents complete tasks, with support for Discord, Slack, Teams, Feishu, Ntfy, and custom webhooks.
    6
    MIT

Matching MCP Connectors

  • Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.

  • Convert any webpage to clean LLM-ready markdown, extraction-first, with article and news modes.

  • Permanently delete a webhook endpoint. The URL stops receiving events immediately and the secret is destroyed; recreate from scratch if you need to re-add it. To pause without losing config, use update_webhook with active:false instead.
    ConnectorNo auth
  • Delete one NACE industry-monitoring subscription by its id (from list_my_subscriptions); Firmaradar then stops delivering webhooks for that industry. The subscription must belong to the authenticated user. Idempotent — deleting an id that is already gone returns already_absent=true rather than an error. Reversible only by re-subscribing. Call only when the user has asked to stop monitoring an industry.
    Connector
    Destructive
    No auth
  • Use this when, and only when, a user mentions receiving an IRS letter or notice and wants to know what it means, the deadline, or what to do. For a state-agency letter, use triage_tax_problem with problem=state_tax instead. Give this tool the IRS notice code (e.g. CP2000, CP14, LT11) and optionally the notice date and amount shown. Set brief:true for a shorter answer.
    ConnectorNo auth
  • What a Trend News Agency subscription costs and what it gives access to: the monthly and annual price in manat, dollars and euro, any introductory offer, and the link to subscribe. Call this when a reader asks what a subscriber-only article would cost them, or asks about subscribing. Reading it does not subscribe anyone — sign-up happens on trend.az, where the reader sees the terms and confirms it themselves.
    ConnectorNo auth
  • List the env vars a project's code can use and the resources behind them: (1) resources CONNECTED to the project — usable as process.env.<NAME> in endpoint code now; (2) the owner's other account-level credentials — reusable, but not usable in code until connected; (3) everything Floot can add. Call it to learn what env vars exist before writing backend code, and BEFORE provisioning or requesting any credential (the owner may already have the one you need). Pass query (case-insensitive substring over names, descriptions, types, and env var names) to filter when the account has many resources. Read-only. Details: get_guides('resources').
    ConnectorOAuth
  • UPDATES an order — its payment status, fulfillment status, and/or tracking number. This MODIFIES live store data and may trigger customer notifications. Ecwid REST: PUT /orders/{orderNumber}. Provide only the fields you want to change. Returns {updateCount}.
    Connector
    Destructive
    No auth
  • List notifications for a workspace. Call this when the user asks what needs their attention. Returns paginated notifications most-recent first. Filter by type to see only specific notifications (e.g. pending_review, credits_exhausted, account_risk, reply_received). Use campaignstack_count_unread_notifications to get the unread badge count. Use campaignstack_mark_notification_read or campaignstack_mark_all_notifications_read to mark as read. Results are one page. When pagination reports more, say so rather than presenting the page as the whole set, and page through before counting anything.
    ConnectorAPI key
  • Reads your latest 20 bell notifications and how many are still unread (reading them here does NOT mark them as read).
    ConnectorAPI key
  • FREE and OPTIONAL intro — you may skip it and call evaluate_symbol / scan_bottoms / scan_tops directly. Agent-to-agent intro & subscription funnel: call with no args (or phase:"hello") to meet this coin-signal agent, then walk phases: "value" (why subscribing earns money) -> "catalog" (all indicators) -> "sample" (live verdict on a symbol) -> "subscribe" (terms). Pass interest:false to bow out. Returns structured JSON with a `next` list of suggested phases.
    ConnectorNo auth
  • Set (or remove) this WhatsApp install's outbound webhook. Owner/admin only. - To set: pass `url` (https only, not localhost). `events` is the list of subscribed events ("permissions") — e.g. ["whatsapp.message"], or ["whatsapp.*"] for every WhatsApp event, or [] / omit for ALL events. See available_events from whatsapp_webhook_get. `include_result` (default true) controls whether the tool result is included in tool.call payloads. `secret` is optional (reserved). - Subscribing to any whatsapp.* event makes the daemon hold a live connection per number and forward inbound messages to your URL. - To remove the webhook: pass `remove: true` (or an empty url).
    ConnectorNo auth
  • Register a custom domain for receiving test mail. Returns the DNS records (TXT challenge + MX) to publish; the domain accepts mail only after verify_domain passes.
    ConnectorNo auth
  • Read one webhook by id. view=webhook (default) returns the subscription; view=deliveries returns recent delivery attempts (status, retries, dead-letter) to debug why an endpoint isn't receiving events.
    ConnectorNo auth
  • Check your notifications (replies, mentions, DMs), newest first. ``count`` is how many notifications this response holds; ``has_more`` is true when more match than ``limit`` allowed. Requires authentication.
    ConnectorNo auth
  • Check your notifications (replies, mentions, DMs), newest first. ``count`` is how many notifications this response holds; ``has_more`` is true when more match than ``limit`` allowed. Requires authentication.
    ConnectorNo auth