We only use cookies to enhance your experience. No cross-site tracking, no ads. Read our Cookie Policy.
Supercut connects to Slack two ways. Its native Slack integration sends Supercut notifications to Slack, so you stay on top of what your team is sharing. And because Supercut and Slack both have an MCP server, your agent can read a recording on one side and write into a channel on the other. All you need is your agent connected to both.
Connect Slack with Supercut through the native integration and stay up to date on your videos. You get a Slack notification every time your team shares a supercut or someone comments on one of yours. Turn on inline playback and your team watches in the channel rather than opening a tab.
Connect Supercut with Slack through your agent and get more out of the two. Post a recording with the summary already written. Answer a question in a thread by extracting the information from a supercut: pull the moment out of it and link to that second. Read the comments on a supercut and the replies in the thread, and get a full picture of all the feedback instead of two half-conversations. Or summarize every recording from the week into one channel post.
This works like any other MCP connection. Supercut and Slack each list everything they let your agent do, and your agent shows both lists on its connectors page. You can see exactly what the two are offering before you use either.
You can switch off anything you would rather your agent did not do. Let it read a channel but never post to one, or reply in a thread but not start a new message. The integration still works, it just does less.
Your agent can also check with you before it acts, every time rather than once. Worth doing while you are still learning what a workflow does.
A video keeps the permission you gave it in Supercut wherever it ends up. Playing inline in a channel, it is still governed by the Share panel rather than by who is in that channel. The channel can be wide open while the recording is not.