Connect an assistant

Your assistant's tools are served from one address, called the MCP endpoint. Any app that supports MCP can use it. This page shows the address and step-by-step instructions for adding it to Claude, ChatGPT, Cursor or a command-line client.

For the technical details, see the MCP guide and the API reference.

What you see

• This tenant's MCP endpoint: the address, with a copy button. It serves the tools your company has published, the same ones your website widget and the Playground use.
• Customer sign-in: the login your customers use when they ask for something personal, marked set up or not set up.
• Setup instructions: tabs for Claude, ChatGPT and Cursor / CLI, each with numbered steps and the exact text to paste.

Every conversation through the endpoint shows up in Live sessions and Tool calls, with the channel mcp.

How to add it to Claude

1. Select the Claude tab.
2. Copy the connector URL.
3. In Claude, go to Settings, then Connectors, then Add custom connector.
4. Paste the URL as the remote MCP server URL and give it a name.

How to add it to ChatGPT

1. Select the ChatGPT tab.
2. Copy the connector URL.
3. In ChatGPT, go to Settings, then Connectors, then Create. Developer mode must be on.
4. Paste the URL as the MCP server URL and choose OAuth.

How to add it to Cursor or a command-line client

1. Select the Cursor / CLI tab.
2. Copy the configuration block.
3. Open the client's MCP config file. For Cursor this is ~/.cursor/mcp.json. For Claude Code it is .mcp.json in the project.
4. Merge the block into the file.
5. Restart the client. Your company's tools appear under this server.

The block includes a sign-in header for local testing. The Act as (local dev) box sets the value of that header, and the block updates as you type. In production, remove the header and the client asks you to sign in instead.

How signing in works

• Public tools work for anyone, as a guest.
• Some tools need a signed-in customer. The first time a customer asks for one of them, the assistant asks them to sign in with your company's login.
• Until your company sets up customer sign-in, customers can only use public tools.
• A sign-in for one company never works for another.

How to set up customer sign-in

Any OpenID Connect provider works: your own Okta, Auth0, Microsoft Entra ID, Amazon Cognito or Keycloak, or a Clerk application set up for your company.

1. Copy the Redirect URI to register at your provider.
2. At your provider, register a web application with that redirect URI.
3. Back in the console, enter the provider's Issuer URL, Client ID and Client secret. You can also change the Scopes; openid is always added.
4. Click Save. The console checks the provider before saving, and the card changes to set up.

To stop signing customers in, click Turn off sign-in. Changing the provider signs out every customer connected through an assistant; they sign in again the next time they ask for something personal.

The assistant never sees your provider's tokens. We check the sign-in and give the assistant a token that only works for your company.

You choose which actions need a signed-in customer in Flows, on each action's trigger step.

Good to know

• The endpoint only serves published tools. Unpublished drafts are not visible to connected apps.