Which apps can a Sume workspace connect today? Four rows
The Sume Integrations page lists four rows: Slack and Meta Ads you connect, plus built-in Remotes and HyperFrames. Gmail, Drive and Linear are not live.
A Sume workspace can connect two outside apps today: **Slack** and **Meta Ads**. Two more rows, **Remotes** and **HyperFrames**, are Sume's own built-ins and are always on. Everything else in the catalog, including Gmail, Google Drive, Docs, Sheets, Linear, Notion and GitHub, is marked coming soon and the dashboard hides it. This page is the current list.
Where the list lives
Open Dashboard, then Integrations. The page renders one flat list of live and built-in rows. It has no category headings and no disabled "Coming soon" buttons, because rows with availability === "coming-soon" are not rendered. The source of truth for ids, copy and categories is packages/studio-agent-core/src/integrations/catalog.ts, and the operator notes are in docs/operations/integrations-catalog.md.
The four rows
| Row | Kind | What you do |
|---|---|---|
| Slack | OAuth connector | Connect with an admin account; agents get read-only slack_* tools |
| Meta Ads | OAuth connector | Connect; agents get reviewed read tools for ad accounts, insights and more |
| Remotes | Built-in | Nothing. It is the first-party hosted MCP at https://mcp.sume.com/mcp |
| HyperFrames | Built-in | Nothing. It is the Agents video editor and composition stack |
Built-ins have no Connect button
Remotes and HyperFrames are kind: "builtin". They always render as connected. There is no Connect, Disconnect, demo or OAuth client for them, and their status does not come from the workspace_integrations table. If you were looking for a button to add the hosted MCP to your workspace, there is none: you point your MCP client at the URL instead. See which URL to put in your client.
What coming soon means in code
The gate is integrationAvailability in policy.ts. When a provider is coming soon, its Connect route, its demos and its agent tools are all disabled, and a saved connection does not appear usable. The /api/integrations payload still reports those providers as coming-soon, which is why ids stay in catalog.ts. The catalog does not include Krea, on purpose.
Who sees the tools
Connected providers give the agents of that workspace read tools. Another workspace gets no tools and no credentials from your connection. Disconnecting removes the credentials, any pending authorization and the tool availability.
- Live OAuth connectors: Slack, Meta Ads
- Built-ins: Remotes, HyperFrames
- Hidden as coming soon: Gmail, Google Drive, Docs, Sheets, Linear, Notion, GitHub and the rest of the catalog
A quick way to decide
Start from the job you need done. If an agent should read Slack threads or look at Meta ad performance, connect that row as an admin. If you want Claude, Cursor or Codex to generate media, you do not need an integration at all: add the hosted MCP URL to the client and sign in or use an API key.
Revisit the page when you plan a rollout, because rows move from coming soon to live only after a registered OAuth app and a reviewed tool list exist. Do not plan around a hidden row; the dashboard only shows what works today.
Related posts
More in Integrations
- Gmail, Drive, Docs, Sheets in Sume: why they are coming soon
Gmail, Drive, Docs and Sheets stay coming soon in Sume until Google Developer Preview enrollment and the read allowlists are verified.
- WordPress media_handle_sideload for a Sume music mp3 attachment
Download the Sume artifact URL with download_url(), then media_handle_sideload() it into the Media Library. It returns an attachment id or a WP_Error.
- Connected-app tools in Sume: plugin prefixes and the mcp:read rule
Tools from a connected app get a provider namespace such as slack_plugin_ or meta_plugin_, need mcp:read, and a plugin outage does not break unrelated tools.
- X media upload APPEND: 5 MB chunks, and how to split a Sume MP4
The X API v2 APPEND step takes chunks of at most 5 MB. Count the segments for a Sume MP4 with a short script before you upload to the initialize endpoint.
Written by Sume