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 that power Data Collections and reporting.
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 Data Collections and reporting.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 behind a Data Collection.
Who sets things up
Not all setup is IT work. Some integrations are pure self-serve OAuth that a builder can do themselves. Others need a one-time IT foundation, then builders self-serve from that point on. A few are admin-only because they use an API key rather than per-user OAuth. The per-provider page for each integration names the actors for each stage.