Connectors
Connectors let your agents act on your behalf in external tools — reading files, creating issues, updating calendars, and more. You set them up per project; agents use them automatically when they have the right permissions.
Connector types
| Type | What you do | When to use |
|---|---|---|
| OAuth | Click Connect, sign in to the provider | GitHub, Google, Notion, Linear — any service with a sign-in flow |
| Manual Credential | Paste an API key or token | Services that issue static API keys (e.g. a self-hosted tool) |
| Custom MCP | Enter your own server URL | Your own MCP server exposing private tools or data |
What you can connect
GitHub, Google Drive, Google Calendar, Notion, Linear, and any service reachable via a Custom MCP server.
Gotchas
- Each connector is scoped to one project. Connecting GitHub in Project A does not make it available in Project B — you connect it separately in each project where you need it.
- You can only connect one account per provider per project. If you need two separate GitHub identities, use two separate projects.
- OAuth tokens from Google and Microsoft expire after a period of inactivity. If a connector stops working, disconnect and reconnect to refresh the token.
- Enabling a connector is not enough on its own. The connector also needs to be in the agent’s allowed tools before the agent can use it.