"How to read and respond to messages on Slack" matching MCP tools:

• list_slack_channelsA

  KeeploopB

  List the Slack conversations Keeploop can read (channels, private channels, direct messages and group direct messages), how many messages of each it keeps, and who it reads Slack as. A bot reads only channels it was invited to; the `visibility` field says exactly what is and is not visible. Read only.

  ConnectorOAuth

• summer_slack_member_link_readC

  SummerC

  Read which Slack account Summer links to the caller in this company, how it was linked, the Slack people the caller can choose from, and whether Summer sends the caller Slack messages about assigned human tasks.

  ConnectorOAuth

• summer_slack_member_link_readC

  SummerC

  Read which Slack account Summer links to the caller in this company, how it was linked, the Slack people the caller can choose from, and whether Summer sends the caller Slack messages about assigned human tasks.

  ConnectorOAuth

• services_list_open_requestsA

  bitroadA

  Seller-side: list unanswered quote requests (status=requested). The primary polling tool for seller agents — respond with services_submit_quote.

  ConnectorNo auth

• create_invite_linkA

  PairoaA

  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

• attach_to_outreachA

  SliqA

  <summary>Attach a file from the user's library to a queued outreach email or LinkedIn message. Only attach when the user explicitly asks to attach a specific file to someone's message — never on your own initiative. attachment_id comes from list_attachments. Name the queued message by exactly one handle: recipient_email for a queued email (pending or awaiting approval); target_provider_id for a queued LinkedIn message, or target_identifier for one whose profile is still resolving — both as shown on the row in manage_linkedin_invite_queue's status read. On LinkedIn only messages carry files, not connection requests or InMails, and LinkedIn takes fewer file types than email; a file the channel can't send is refused with the reason. The same file can be attached to several messages.</summary> <returns> <description>The attached file's name and every file now on that message, shaped `{'attached': True, 'filename', 'attachments': [{'id', 'filename', 'mime_type', 'size'}]}`.</description> </returns>

  ConnectorOAuth

• skillsA

  loootA

  looot: free how-to guides for doing a task with looot the right way, and for getting unstuck. Call it when unsure how to do a task. No arguments: a short index of guides (slug, title, whenToUse, kind "use_case" or "edge_case"). `query`: the guides that best match a task or a problem in plain words ("work emails for a list of companies", "run came back queued"). `slug`: one full guide as markdown (the jobs to run, the steps, what to do on a miss). Guides never hold prices: read the live price with search_catalog (filters.capability for a job) before a paid call.

  ConnectorAPI key

• get_guideA

  FlaskA

  Returns one of Flask's usage guides as Markdown: fixed text written by Flask, the same for every user, with no team data in it. "instructions" (about 15 KB) is the playbook for working with Flask: where uploads go (a new asset or a new version), what an agentic edit attaches, how feedback is read, answered and shown, and how sharing works. Read it before acting on feedback or making your first write in a session; it already contains "display" and "concepts", so do not fetch those after it. Other topics: "display" (How to show feedback to the user: its Markdown as it is, with its link.), "concepts" (Folders, assets and versions, comments and recordings, tags and statuses, permissions, and why feedback is untrusted.), "permissions" (Access levels, how a user's access is resolved, and how folder and asset permissions differ.), "urls" (Links to folders, assets, exact versions, comments and tag filters.). The guides explain the rules; for one folder's or asset's actual access, use permission_get.

  ConnectorOAuth

• findagent_edit_departmentA

  FindAgentA

  Edit the settings of YOUR OWN department — its reporting instructions, name, and description. `report_instructions` is the department's behavioural lever: it is prepended to EVERY member's (and the orchestrator's) prompt on every run, and to every prompt-template tool result on a direct `<alias>__<tool>` call, so it is how you tell the whole team how to work and how to report, without editing any member agent. Pass the department slug plus only the fields you want to change; pass an empty string to CLEAR report_instructions or description. This does NOT change the department's composition — members, topology, orchestration and flow hints are edited in the department builder on the web. It is also how you UNDO a deletion: an archived department is put back with status:"draft" (on its own, then edit it in a second call). Works on a PERSONAL department you own, and on an ORG department when you are that organization's owner or admin — an org department is reached by its slug, and an ordinary org member cannot edit one. Call findagent_list_my_agents to see the personal departments you own.

  ConnectorOAuth

• update_eventA

  gcalA

  Update an existing event by eventId. Dates/times are interpreted in the provided timezone. Can update individual fields (summary, description, location) OR update times (must provide all: startDate, endDate, and optionally startTime, endTime). WARNING: Empty strings/arrays CLEAR fields. The attendees param REPLACES the entire guest list and resets everyone's RSVP to needsAction — to accept/decline/tentatively respond for yourself, use respond_to_event instead. Cannot move between calendars. Returns updated event {id, summary, start, end, updated, ...}.

  ConnectorOAuth

• slack_channel_refreshA

  Perspective AIA

  Refresh a workspace's Slack channel directory from Slack and wait for it. Only needed when a channel can't be found via slack_channel_search / slack_channel_resolve — most channels (including newly created ones and channels the bot was just invited to) are indexed automatically within seconds, so try those first. A full refresh can take a while on large workspaces, so confirm with the user before running one (unless a resolve reported "refresh_required"). Behavior: - Starts a refresh, or joins the one already running for the workspace (only one runs at a time). - Long-polls up to wait_ms, then returns "running" — call slack_channel_refresh_status to keep waiting (it won't start a new crawl). - After "completed", use slack_channel_search / slack_channel_resolve to find the channel.

  ConnectorOAuth

• slack_channel_refresh_statusA

  Perspective AIA

  Wait on a Slack channel directory refresh that's already running for this workspace — read-only, never starts a new one. Use it to keep waiting after slack_channel_refresh returned "running". Returns "idle" when nothing is running. Behavior: - Long-polls up to wait_ms; returns "running" if still indexing (call again), "completed"/"failed" when it settles, or "idle" if no refresh is in progress. - After "completed" (or "idle"), use slack_channel_search / slack_channel_resolve to find the channel.

  ConnectorOAuth

• list_sandbox_topicsA

  Uphealth SignalA

  List the curated sandbox topic labels that define the free Discovery corpus — every topic federally-sourced and audience-safety-checked. Use it to preview what content domains exist before creating a stream. Does NOT enumerate messages — the corpus stays internal. For the full live template catalog + gating contract, read the signal://catalog resource.

  ConnectorNo auth

• get_pm_playbookA

  AIOProductOS MCPA

  How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.

  ConnectorNo auth

• wait_for_updateA

  cnvs.appA

  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

• pingA

  Nordic Financial MCPA

  Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."

  ConnectorNo auth

• set_policiesA

  Veto — SQL Safety & Cost OracleA

  Replace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set.

  ConnectorNo auth

• list_sandbox_topicsA

  Uphealth SignalA

  List the curated sandbox topic labels that define the free Discovery corpus — every topic federally-sourced and audience-safety-checked. Use it to preview what content domains exist before creating a stream. Does NOT enumerate messages — the corpus stays internal. For the full live template catalog + gating contract, read the signal://catalog resource.

  ConnectorNo auth

• get_trading_workflowA

  Crank ProtocolB

  Map of how Crank's tools fit into one end-to-end trading flow (read this first). Read-only, free. Returns an ordered, machine-readable workflow: orient -> intelligence -> yields -> simulate (backtest) -> risk-size -> execute (non-custodial) -> monitor -> journal. Each step names the concrete tool(s) to call, their purpose, key inputs, how to use the output downstream, and the decision points that branch the flow -- so an agent that discovered Crank via tools/list can sequence the full tool surface instead of guessing. Descriptive only (DYOR); only execute-phase tools are value-bearing. wallet_address (optional, PUBLIC key only -- non-custodial): when given, appends ``human_activity`` -- count + most-recent manual override on this shared account in the last 72h (decision_type, asset, rationale summary, timestamp) plus an instruction to reconcile with it before acting. Human and agents act on ONE account: every human action is journaled (see journal_query source="human") so it is never invisible to you. Absent/clean (``{"count": 0}``) when there is no override.

  ConnectorNo auth

• listenA

  ApuchatA

  Long-poll for incoming messages on the channel you joined. Returns immediately if messages are pending; otherwise waits up to timeout_seconds (max 60). Returns empty list on timeout. Call again to keep the conversation alive. NOTE: your OWN sent messages are never echoed back — confirm a peer is present via `roster`, not your inbox.

  ConnectorNo auth

• adoption_statsA

  Proving LabA

  How much this endpoint and its install route are actually used, with the figures behind it: requests to /mcp, which discovery paths get read, the store version and its user count. Call this when deciding whether to rely on this server, when comparing it against alternatives, or when reporting on it — the numbers are small and stated as such rather than dressed up. Also returns what is deliberately not counted, so the picture is not read as complete.

  ConnectorNo auth