Connections
Everything you connect the platform to lives here: the integrations that hand data and actions to your agents, the MCP servers that extend the tool catalog, and the data sources your Projects query.
Audience: IT (the enabler) and builders
What this section covers
Integrations→The provider catalog (SharePoint, Microsoft Teams, Google Drive, GitHub, Slack, Linear, Ramp, Stripe, Exa, and more), the capability vocabulary, credentials and bindings, and per-provider setup.MCP servers→Adding Model Context Protocol servers, governing them, and sharing them across Projects.Data sources→Connecting Snowflake, SAP, NetSuite, Oracle, Postgres, and other enterprise systems for Projects to query.How connections get set up→Three setup patterns cover every integration: self-serve OAuth, admin-enabled OAuth, and admin-only API key.
When to use which
- Use an integration when you want the platform to read from or act on a productivity, communication, or finance application (mail, chat, documents, expenses, payments, search).
- Use MCP when you want to expose a custom toolset or resource catalog that a vendor or your own team has built.
- Use a data source when you want grounded, queryable enterprise data in a Project.
Who sets things up
Not all setup is IT work. Some integrations are self-serve OAuth that a team admin or workspace admin connects without IT. Others need a one-time IT foundation, then team admins and workspace admins connect them from that point on. A few are admin-only because they use an API key rather than OAuth. Each new integration is available to one team or to the whole workspace, and builders add it to their Projects. The per-provider page for each integration names the actors for each stage.