Set up
Integrations
An integration is a connection that gives agents tools in another service, such as GitHub, Linear, Gmail or Stripe. Adapt supports remote MCP servers, Composio, Executor, Google Workspace, Windsor.ai and Adapt Platform's connected services.
How an integration reaches an agent
Three things decide whether an agent can call a service:
- A connection. Someone adds it on Connections, with the credentials or sign-in the service needs.
- Availability. A connection's Available to workspace agents switch is on by default. Turn it off to pause the connection without losing its setup; agents can't use it while it's off.
- The agent's selection. Each agent lists the integrations it uses and, for each, the services or individual tools it may call. Selecting none exposes nothing. New agents copy the integrations in Agent defaults; later changes to the defaults don't touch existing agents.
When you connect a workspace integration, the connect dialog offers to add it to the agents you can edit.
A connection that is on is permitted for use, not verified. Its credentials can expire or lose access after you save it, and a setup check passes only for what it checks (for example, Executor's check covers API and catalog access, not each account behind it). Agents report a tool that didn't load instead of skipping it silently.
Workspace and personal connections
When you connect an integration, you choose who it's for:
- Everyone in the workspace. Agents use the account for everyone. Only owners and admins can add these.
- Just you. A personal connection. Agents use it only on runs you start. Any member can add one, and other members can't see it.
On your runs, an agent tries your personal account first. If the service rejects your credentials, the call can fall back to a workspace account that has the same tool; other failures don't fall back. The agent's tool selection applies to personal accounts too. Leaving or being removed from a workspace deletes your personal integrations there.
Connect an MCP server
Adapt connects to remote MCP servers over Streamable HTTP; local stdio servers aren't supported. Connections lists about 130 built-in servers, including GitHub, Linear, Notion, Sentry and Stripe. To add any other server, choose Add an MCP server and paste its URL.
A server signs in one of three ways:
- Sign in. OAuth in a new window. Adapt registers itself as a client where the server allows it. Otherwise, open Advanced and enter a client ID and secret from an OAuth app you create with the vendor, using the redirect URL shown,
<APP_URL>/api/integrations/mcp/callback. An app with a client secret also needs the exact OAuth issuer URL from the vendor's app settings. - Access token. Paste an API key. Adapt sends it in the
Authorizationheader afterBearer, unless the key names its own scheme, such asBasic …. Advanced lets you change the header for a new server. - No sign-in. The server is open.
A pasted server becomes a card for the whole workspace, even when its connection is personal; only the credentials are personal. Agents see each tool as mcp__<connection>__<tool>. Tools the server marks read-only count as reads; everything else counts as a write.
Connect Composio
Add a Composio connection with a project API key (ak_…, from Project settings → API Keys in Composio, full access). The connection's page lists the project's toolkits; connect each toolkit's account there. Agents then choose toolkits. A workspace connection shares one Composio user across the workspace; personal connections get their own. If a toolkit isn't connected, the agent can give you a link to connect it.
Connect Executor
Add integrations in Executor first, then add an Executor connection:
- Executor API URL: the API root, for example
https://executor.sh/api. It must be reachable from the Adapt server. - Executor workspace URL: the browser URL of the same Executor workspace, for example
https://executor.sh/acme. Account sign-ins open here. - Executor API key: a key scoped to that workspace. Leave it blank only for a local deployment without auth.
Adapt lists Executor's catalog and opens Executor's own setup to connect accounts. Every member using the connection shares the accounts the key can see. Tools that may ask for more input aren't auto-approved; they pause and must be finished in Executor. Disconnecting removes the accounts the key can see but doesn't revoke grants at the upstream service.
Connect Google Workspace
Google Workspace uses your own Google Cloud service account with domain-wide delegation, not an OAuth sign-in.
- Create a service account and a JSON key. Paste the key into Service account key. Treat it like an admin password: it can act as anyone in your domain within the scopes you authorize.
- In Act as, enter the Workspace user agents act as. A dedicated user such as
agent@keeps activity clear. - Set each app to Off, Read or Read & write: Gmail, Calendar, Drive, Docs and Sheets. The directory is read only. Apps default to Read.
- Save. The setup check shows the client ID and scope list. A super admin pastes them in the Google Admin console under Security → API controls → Domain-wide delegation. The check also confirms each app's API is enabled in the service account's Cloud project.
Write tools exist only for apps set to Read & write. Changing an app's access changes the scopes, so update the Admin console entry to match.
Connect Windsor.ai
Add a Windsor.ai connection with an API key (Settings → API Access in Windsor.ai). Connecting a data source opens a Windsor.ai co-user link. For each connector an agent selects, it gets a tool to list accounts and fields, a query tool for reporting data, and one tool per Windsor.ai action. Revoking unlinks co-user accounts only; remove accounts added in the Windsor.ai dashboard there.
Use Adapt Platform services
An agent whose sandbox is an Adapt Platform connection (see Sandboxes) can also use the services connected in that Platform organization. It gets two tools: one searches the approved services for operations, the other runs Python in a fresh Platform sandbox that calls them. Credentials stay in Platform. When a service needs a sign-in, the agent gives you a link, or tells you an organization admin must connect a shared account.
Tool calls and uncertain outcomes
Every tool call appears in the chat as it runs, and owners and admins see each call and its outcome in Settings → Activity log. Adapt doesn't retry a failed integration call on its own. A call that fails partway may already have changed something in the service, so its outcome is uncertain, not failed. Check the service before you ask the agent to repeat it.
Adapt checks the agent's access before each call. If the connection, its credentials or the agent's selection changed during a run, the call stops and asks you to start a new message.
Limits
- Integrations per agent: 16.
- Services per integration on an agent: 50. Individually selected tools: 1,000.
- MCP tools per connection: 200. Larger servers expose their first 200, in the order the server returns them.
- Executor tools per integration: 50.
- Tool names are cut to 64 characters, the length model providers accept.