Skip to main content
Give an agent reach beyond the browser, sending a Slack message, sending an email, by connecting an integration first and then naming it when you submit a run.

​
Setup

Connecting an integration is a human-only step, it has no MCP tool. Do it from the console or the CLI first:
Then connect the MCP server as usual for the agent side, see setup.

​
What you’ll do

  • Connect a Slack or Gmail-style integration from the console or CLI
  • Submit an agent run that names it explicitly
  • Let the agent call that integration’s tools mid-task

​
Example exchange

“Research this topic and post a summary to #research on Slack when you’re done.” Because the Slack integration was already connected and this run named it at submit time, the agent’s task can end with a message posted through it. If the run had not been given that integration explicitly, it would have no reach to Slack at all, connecting a server to the workspace is not the same as granting one run access to it.

​
What it can’t do

An assistant cannot connect the integration itself, no MCP tool exists for integrations.connect, list or delete. That consent step is a person’s alone, every time.