Docs/Claude
#

Claude

export const meta = { title: 'Claude integration', description: 'Connect Canary to Claude.ai, Claude Code, and other MCP-compatible clients with OAuth-based setup so Claude can work with your Canary workspace.', tags: ['integration', 'claude', 'mcp', 'oauth'], };

Connect Canary to Claude.ai, Claude Code, and other MCP-compatible clients with a dedicated install flow. Use OAuth-based setup to sign in, choose your organization, and let Claude access the Canary context you want to work with.

01Prerequisites

Before you connect Claude to Canary, make sure you have:

  • A Canary account with access to the workspace or organization you want to use
  • Permission to authorize integrations for that organization
  • Access to one of the supported clients:
    • Claude.ai
    • Claude Code
    • Another MCP-compatible client

If you manage multiple organizations, decide which one Claude should use before you start. You can change the selected organization later by reconnecting the integration.

02Setup

Set up the integration from the dedicated Canary install experience for your client. The install page provides client-specific connection options and branded connector details so you can confirm you are authorizing the correct Canary integration.

Claude install page showing connection options for different clients

Connect from Claude.ai

Use this path if you want to connect Canary directly inside Claude.ai.

  1. Open the Canary Claude install page.
  2. Select the Claude.ai tab.
  3. Click the option to connect with Claude.ai.
  4. Sign in to Canary if prompted.
  5. Review the OAuth consent screen.
  6. Choose the Canary organization Claude should access.
  7. Approve the connection and return to Claude.ai.

After setup finishes, Claude.ai can use the Canary connector in the authorized organization.

Connect from Claude Code

Use this option if you work from Claude Code and want to connect through the same OAuth-based flow.

  1. Open the Canary Claude install page.
  2. Select the Claude Code tab.
  3. Copy or launch the connection flow shown for Claude Code.
  4. Complete the Canary sign-in and OAuth consent steps.
  5. Choose the organization you want Claude Code to access.
  6. Finish authorization and confirm the connection in Claude Code.

If Claude Code prompts you to approve or trust the connector after authorization, complete that prompt before you begin using Canary tools.

Connect from other MCP clients

Use this option for any client that supports MCP connections.

  1. Open the Canary Claude install page.
  2. Select the Other MCP clients tab.
  3. Copy the MCP endpoint or discovery URL shown on the page.
  4. Add a new MCP server or connector in your client.
  5. Paste the URL provided by Canary.
  6. Start the connection flow from your client.
  7. Sign in to Canary, review the OAuth request, and select your organization.
  8. Save the connection in your MCP client.

If your client supports MCP discovery, use the discovery URL from Canary. If it requires a direct endpoint, use the MCP endpoint shown on the install page.

03Configuration

After you connect Claude, review how authorization and endpoint selection work so you can troubleshoot or reconnect quickly.

Canary uses OAuth for Claude integration setup. This means you do not need to create or manually manage an API key for the supported install flow.

During authorization, you:

  1. Sign in to your Canary account.
  2. Review the access request.
  3. Select the organization Claude should use.
  4. Approve the connection.

If you belong to multiple organizations, make sure you select the correct one. Claude only sees the Canary data available through the organization you authorize.

Reconnect the integration if you need to switch organizations or if an admin changes your access.

MCP endpoint and discovery URLs

Different clients connect to Canary in different ways:

OptionUse it whenWhat to do
MCP endpointYour client asks for a direct server URLPaste the endpoint into your client's MCP server configuration
Discovery URLYour client supports MCP discoveryPaste the discovery URL and let the client resolve the connection details

Always copy these values from the Canary install page for the client you are setting up. This helps you avoid formatting mistakes and ensures you use the current connection details.

04Usage

Once connected, you can use Claude to work with Canary from your authorized organization. The exact prompt and workflow depend on your client, but the connection gives Claude access to Canary context through the installed connector.

What Claude can access in Canary

Claude can only access the Canary organization you approved during OAuth setup. Use this connection when you want Claude to help you work faster with your Canary data and workflows.

Depending on your workspace access, Claude can help you:

  • Explore relevant Canary resources in the connected organization
  • Answer questions using the context available through the integration
  • Support investigation and workflow tasks that depend on your Canary workspace data

If you need broader product context while you work, see related Canary docs such as /docs/reference/api-catalog and /docs/reference/flows.

Troubleshooting connection issues

If the connection does not work as expected, try these steps:

  • Confirm you selected the right client tab on the Canary install page
  • Sign out and restart the OAuth flow if authorization appears incomplete
  • Make sure you chose the correct Canary organization during consent
  • Recopy the MCP endpoint or Discovery URL if your client reports an invalid configuration
  • Check whether your client requires an extra approval step after OAuth completes
  • Reconnect the integration if your organization access changed

If Claude connects but cannot access the expected workspace data, the most common cause is that the wrong organization was selected during setup. Reauthorize the integration and choose the correct organization.

If the issue continues, contact your Canary admin or support team with the client you are using and the point where the connection fails.