Add a new connection

Before you add an installation

Use an active administrator account and switch to the Admin workspace. Identify the upstream organization or workspace you intend to connect, the person who can authorize it, and a read-only operation that can verify access without changing company data.

• For a built-in provider, check the setup guide for its available authentication path and any deployment requirements.
• For a custom server, obtain its public HTTPS MCP endpoint and confirm that it supports the current Streamable HTTP and provider OAuth workflow.
• Decide whether access should be organization-wide or limited to one or more teams.
• Complete payment setup before production activation, including activation of the first free connection.

Add a built-in provider

Built-in providers have guided setup with four steps: sign in with your provider account, discover available tools, review permissions, and test and enable.

1. Go to Connections and click Add connection.
2. Select a provider from the directory (GitHub, Jira, Slack, Gmail, Google Drive, Google Docs, Google Calendar, Linear, Notion, or Sentry).
3. Save the draft, then use Sign in to provider in its connection setup guide.
4. Discover available tools, review their permissions, and complete the read-only readiness test. A discovered schema also needs a verified validator release.
5. Inspect the setup status and resolve any blockers before accepting the activation preview.

Add a custom MCP server

Register a remote MCP server by providing its endpoint and setup preferences. Compatibility, authentication, and reviewed tools are checked separately before activation.

1. Go to Connections and click Add connection.
2. Choose Custom MCP server.
3. Enter the server endpoint URL — it must be a public HTTPS URL.
4. Choose Streamable HTTP. The current connection setup and execution path does not support legacy SSE transport.
5. Save setup, then complete provider OAuth and discover tools through the connection setup guide.
6. Review discovered permissions and complete testing before enabling the connection.

Enable the connection

Enabling requires provider acceptance, current authentication, reviewed tool validators, a recent successful read-only test, and acceptance of the current billing preview. If the guide reports a blocker, resolve it and test again; saving a draft or completing consent does not bypass it.

Review discovery before you trust the tool list

Discovery is an inventory step. It does not make every returned tool executable. Review the tool’s action, resource boundary, required scopes, and schema before testing it. A read-sounding name is not proof that an operation is harmless.

A discovered tool that lacks a verified validator release remains blocked even if provider sign-in succeeded. Resolve the indicated review or validation requirement through the supported deployment process. Saving another draft or changing the display name does not resolve that requirement.

Verify activation from a member account

After enabling the installation, check it from the identity that will actually use it. Administrator setup evidence does not establish another person’s personal provider access.

1. Open the personal workspace as an intended member of an assigned team.
2. Complete that person’s provider authorization and connection test if requested.
3. Discover the tools in the MCP client and run the reviewed read against an allowed resource.
4. Match the result with the person, connection, decision, and outcome in activity.