"Servers that support Server-Sent Events (SSE)" matching MCP tools:

• rename_folderA

  Mailbox MCPA

  Rename a folder, or move it under a different parent - in IMAP these are the same operation, because a folder's name is its path. Pass `parent` to reparent it while keeping its name. THE MESSAGES INSIDE COME WITH IT, and so do any sub-folders: renaming "Projects" also moves "Projects/Q1", and the result lists every child that moved. REFUSES to rename INBOX (on IMAP that empties your inbox into a new folder rather than renaming anything) and refuses to rename Sent, Drafts, Trash, Junk or Archive (mail clients find those by a flag, not by name, and renaming one can leave your sent mail split across two folders). It also refuses a name that is already taken rather than risk merging two folders. Read the refusal and tell the user what it says - each one is protecting something.

  Connector

  Destructive

  OAuth

• account_support_accessA

  AMZ VaultB

  Grant or revoke the AMZ Vault support team's READ-ONLY view of this account: action=grant lets support see what the user sees for 7 days (auto-expires, they can change nothing, and every view notifies the user); action=revoke turns it off immediately. This changes who can access the account, so it ALWAYS needs the user's explicit go-ahead — offer it only when support needs to see a problem first-hand (usually alongside an account_feedback thread).

  Connector

  Destructive

  OAuth

• save_payment_linkA

  financeA

  Save (or update) the external payment URL for one payment context. Use when the user gives or corrects a link — e.g. "for child support use https://childsupport.state.mn.us". Saving a label that already exists (case-insensitive) UPDATES that link's URL. Intended for URLs the user explicitly provided or confirmed, not found, guessed, or constructed ones. https only; a bare domain like "chase.com" is normalized to https://; javascript:/http:/IP-literal/credential-bearing URLs are rejected. Args: label: The payment context name (max 100 chars), e.g. "child support". url: The user-provided payment page URL (https). Returns: {"success": True, "created": bool, "payment_link": {...}} — created is False when an existing label's URL was updated.

  ConnectorAPI key

• stream_taskA

  TunnelMind Data APIB

  Opens a persistent SSE connection that emits events as the task progresses. The stream closes automatically when the task reaches a terminal state or after ~90 seconds (timeout). Heartbeat comments are sent every ~15 seconds to keep the connection alive through proxies. Event types: - `status` — emitted when status changes (pending → running → complete/failed) - `result` — emitted on `complete` with the full result payload - `error` — emitted on `failed`, `cancelled`, or `expired` with error info - SSE comment (`: heartbeat`) — keepalive, no data Use this tool when: - You want real-time progress without polling. - You are in an environment that supports SSE (EventSource API). Do NOT use this tool when: - You want a simple one-shot status check — use `get_task` instead. - Your HTTP client doesn't support streaming responses. Inputs: - `task_id` (path, required): 26-char ULID. Returns: - SSE stream (`text/event-stream`). Each event is `event: <type>\\ndata: <json>\\n\\n`. Cost: - Free. Counts as one request against rate limits when the stream opens. Latency: - First event: <200ms. Stream duration: up to 90s.

  ConnectorNo auth

• find_my_phoneA

  ReflectoA

  Ring the user's phone at full volume for up to 60 seconds, even if it's on silent or Do Not Disturb. Use this when the user asks to locate or ring their phone. Fire-and-forget: the server can't confirm the phone actually rang, only that the ring request was sent.

  ConnectorOAuth

• send_team_feedbackA

  stubB

  Pass the entrepreneur's feedback, praise, complaint or feature request to the stub team, who read it in Slack. Use this whenever they ask you to send something on — "send this to the team", "tell stub that…", "can you report this", "they should fix…" — and offer it when they voice a clear frustration or want something stub cannot currently do. Quote their own words rather than summarising them. This is NOT feedback about the MCP tools (that is send_feedback), it does not open a support ticket, and nobody will reply in the chat — say so. ALWAYS check the returned `sent` field: when it is false the feedback reached nobody, and you must tell them it did not go through instead of thanking them for it.

  ConnectorOAuth

• submit_feedbackA

  Manifold MCPA

  Sends a report to the Manifold team: an error a tool returned, data that looks wrong, a tool or parameter that is missing, or anything the user asks you to pass on. Free. Use when: a call failed in a way its typed error does not explain, a result contradicts itself or the source, the same ProviderUnavailable keeps coming back, no tool answers what the user needs, "tell Manifold that...", the user's answer when a result's meta.feedback_request had you ask for feedback (prompted true). Tell the user what you sent. Not for: retrying a call; follow the typed error first. Asking for help with a task; this sends no reply. Contacting a person or a company; this reaches only the Manifold team. Returns: Record. feedback_id, to quote if the user contacts support. Cost: 0 credits. Up to 20 reports per workspace per day; over that, ProviderUnavailable with retry_after_s. Example: {"kind": "error", "tool": "seo_get_serp", "request_id": "3f1c9a2e-8d4b-4c6f-9e1a-7b2d5c8f0a13", "message": "seo_get_serp returned ProviderUnavailable five times in ten minutes for the keyword crm for startups."}

  ConnectorAPI key

• create_custom_calendarA

  SFomo: Bay Area eventsA

  Build a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on SF Events (open_on_sf_events; give the user this first), subscribe links (Google Calendar, Apple/Outlook webcal, plain .ics) and a preview. The calendar refreshes itself every few hours, so new matching events keep appearing. An event is included if it matches ANY interest and no exclude term. Nothing is stored by SF Events: the interests are encoded in the link itself. Interview the user first (see the custom_calendar prompt), check matches with search_events, and call this again to adjust. For a one-off answer rather than a standing calendar, use search_events. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  ConnectorNo auth

• volanea_create_workflowA

  VolaneaA

  Create an event-triggered automation workflow from a node/edge graph. Created as a DRAFT — verify it with volanea_test_workflow, then activate explicitly via volanea_update_workflow { status: 'active' }. Idempotent by name. Triggers: "event:<name>" (a product event sent to POST /v1/events or the volanea_track_event tool), "contact.created", "segment:enter:<segmentId>", "segment:exit:<segmentId>".

  ConnectorNo auth

• volanea_create_workflowA

  VolaneaA

  Create an event-triggered automation workflow from a node/edge graph. Created as a DRAFT — verify it with volanea_test_workflow, then activate explicitly via volanea_update_workflow { status: 'active' }. Idempotent by name. Triggers: "event:<name>" (a product event sent to POST /v1/events or the volanea_track_event tool), "contact.created", "segment:enter:<segmentId>", "segment:exit:<segmentId>".

  ConnectorNo auth

• hub_update_purchase_orderA

  Final POS – Custom POS BuilderA

  Rewrite an order that has not been sent yet. ONLY works while it is `suggested` or `draft` — a sent or received order is refused, because the supplier already has it. This REPLACES the whole order: the lines and charges you pass become the order, and anything you leave out is dropped. Read it with get_purchase_order first and send the full set back. This is also how a suggestion is ACCEPTED: editing a `suggested` order turns it into a `draft` and gives it its PO number. To accept one unchanged, pass its existing lines back verbatim.

  Connector

  Destructive

  OAuth

• watch_eventsA

  ctxstore — memory that follows you across modelsA

  Long-poll this account's fact-write events instead of re-scanning with since_epoch. Every store/supersede/delete/archive/restore/move publishes one event {key, id, namespace, layer, op, ts, seq}. One call waits up to max_wait_s (max 25) for the first matching event and returns up to 50, plus next_since. MCP has no streaming here, so loop: pass next_since back as `since` on the next call and nothing is missed (the server keeps the last ~10000 events per account). Omit since to start from now; since=0 replays what is retained; a bare integer N returns events with seq > N. EXAMPLES - Wait for hands to post results: watch_events(prefix='task:pr27-review:result:', max_wait_s=25) - Resume: watch_events(prefix='comms:<your-agent-id>:', since='<next_since>') Inside a workspace only events for keys the grant can read are returned. Long-lived clients can use GET /api/v1/events (SSE) instead.

  ConnectorNo auth

• set_supportA

  FERS — structural FEMA

  Write a nodal support (boundary condition) and point one or more nodes at it: creates or overwrites an entry in model.nodal_supports and sets node.nodal_support on every node you name. Returns the updated model — feed it to solve_model. All 7 DOFs are set independently, in the GLOBAL frame: X/Y/Z (translations), RX/RY/RZ (rotations about the global axes) and warping (the 7th DOF, only live when analysis.options.include_warping is true and the section has i_w). Condition types are case-sensitive: Fixed (rigid), Free (no restraint), Spring (needs the matching <DOF>_stiffness > 0 — N/m for translations, N*m/rad for rotations), PositiveOnly (one-way: may only push in the +global direction, i.e. lift-off) and NegativeOnly (the mirror image). A one-way condition may also carry a <DOF>_stiffness, which from engine 0.2.65 is the bedding stiffness it acts through while in contact — a base plate on a slab is not infinitely stiff. Released, it is free regardless. On 0.2.64 and earlier that number was accepted, range-checked and then silently discarded, so the model solved as rigid contact. THERE IS NO "FREE BY OMISSION". Once a node references a support, any DOF you leave out is treated by the solver as FULLY FIXED — a support of literally {"id":1} is an encastre, and the OpenAPI text claiming an absent field means free is wrong. This tool therefore always writes all six translation/rotation conditions explicitly, and anything you do not name is written as Free. Use `preset` to fill them in one go: fixed (encastre), pinned (X/Y/Z fixed, rotations free), free, roller_x/roller_y/roller_z (ONLY that translation fixed, everything else free), ground_contact_y (X/Z fixed, Y PositiveOnly, rotations free — a base plate that can lift off). Per-DOF fields are applied on top of the preset. Warping is the one exception: leaving it out really does mean free. ONE-WAY SUPPORTS have a prerequisite this tool checks for you: analysis.options.rigid_strategy must be RigidMember (LinearMpc is a hard validation error). Tension/Compression members are fine alongside them from engine 0.2.65 -- before that the combination was refused at validation, so if you are reading advice written against an older engine, that restriction is gone. There is also a SILENT prerequisite — the release tolerance is 0.5*axial_slack in force units, so a coarse axial_slack leaves the DOF engaged while still reporting its reaction as 0, and the printed reactions stop summing to the applied load. This tool lowers axial_slack to 1e-3 when it writes a one-way condition (set keep_axial_slack to skip that). Beware that a support which lifts off can leave the structure unrestrained, and that a one-way support can break an eigen solve if the model also has a modal or buckling block. Reactions use ONE SIGN CONVENTION for every support type from engine 0.2.60: each row is the force the support applies to the structure, so reactions can be summed against the applied load without checking which kind of support produced each one. (Up to 0.2.59 a Spring DOF reported the spring force k*u, the negative of what a Fixed DOF reported for the same physical situation. If you are reading results solved on an older engine, that flip is still in them.) A stiffness curve (stiffness_curves) makes the spring load-dependent, forces the DOF to Spring and requires a NONLINEAR analysis order — and note its driver is the EXTERNAL nodal load at that node, not the reaction, so a base-plate curve with no direct nodal load degenerates to the first point's stiffness.

  ConnectorAPI key

• setThreadReplyingA

  NextmailB

  Tell the team you are writing a reply to an email thread, so getThreadTeam and the app show the others that you are replying and nobody answers twice. The mark lasts 30 seconds, so call it again while you are still writing, and with replying false once you have sent the reply or given up.

  Connector

  Destructive

  OAuth

• getmattered_cancel_applicationsA

  GetMatteredA

  Cancel applications that are queued to be sent or still being prepared, so they are never submitted. Nothing is sent to the employer. A cancellation cannot be undone with these tools. An application that was already submitted cannot be cancelled or withdrawn, and the answer says so for each one. Pass 1 to 25 application_ids from getmattered_get_applications. Cancel only when the user asks. Do not use it for an application waiting for the user's review; use getmattered_reject_applications. Next: getmattered_get_applications to see the new status.

  Connector

  Destructive

  No auth

• getmattered_cancel_applicationsA

  GetMattered (moved)A

  Cancel applications that are queued to be sent or still being prepared, so they are never submitted. Nothing is sent to the employer. A cancellation cannot be undone with these tools. An application that was already submitted cannot be cancelled or withdrawn, and the answer says so for each one. Pass 1 to 25 application_ids from getmattered_get_applications. Cancel only when the user asks. Do not use it for an application waiting for the user's review; use getmattered_reject_applications. Next: getmattered_get_applications to see the new status.

  Connector

  Destructive

  No auth

• list_message_activityA

  MondovoA

  Read a site’s sent and scheduled automation message activity. Filter by SMS, email or WhatsApp, contact, or delivery status. Returns only the recipient, safe body preview, provider status/id and safe failure reason; it never returns provider credentials or private journey configuration. Paginated; compare total with limit and offset. To count what was sent in a period ("how many emails did we send yesterday"), pass sent_after / sent_before for that day in the user's timezone (an ISO date-time with its offset, e.g. 2026-10-28T00:00:00+05:30) with status sent and limit 1, and read `total`: never count a page of messages.

  ConnectorOAuth

• decide_cardsA

  HeyReagent LinkedIn MCPA

  Decide many waiting cards at once, after the user said so ("send them all", "skip these"). decision "send": every message, invitation, comment, reply or accepted invitation among them is checked again as it goes and sent; one a check holds stays waiting with why, and posts, InMails, profile changes and withdrawals are never sent this way (decide those one by one with decide_card). Leave out cardIds to send every such card that is waiting. decision "skip" drops each, with the reason when given.

  Connector

  Destructive

  OAuth

• get_invoiceA

  BillstrideA

  Returns one invoice in full: sender and recipient details, dates, totals in cents, line items, discounts and recorded payments. Use it to review an invoice, or to get the complete current values that update_invoice needs sent back. Read-only. Takes an invoice id from list_invoices; it cannot look up by invoice number.

  ConnectorOAuth

• instatus_update_maintenanceA

  InstatusA

  Reschedule or reword a maintenance that has not finished: change its title, times, affected components or the text of its first message. The change is public immediately and subscribers are not notified. Times keep the same length unless both are sent. To post a new progress message use instatus_add_maintenance_update.

  Connector

  Destructive

  OAuth

• search_eventsA

  NunifyB

  Search for events you have access to by event name or event code. Returns up to 10 matches: ongoing events first, then events nearest in time. Use the returned event ids for future event-scoped tool calls. Each event's start_time and end_time are local datetimes in that event's own timezone (named in the timezone field), without an offset designator. This searches event names only - content inside an event (sessions, speakers, polls, locations, ...) is not searchable here: find the event first, then use that domain's read tool, e.g. read_agenda with action list_sessions and a query for session titles.

  ConnectorOAuth