Claude auto-connect lets you set up Pendo MCP server access in Claude once for members of your organization. Claude confirms who each member is, so members can use Pendo in Claude without signing in or approving access themselves. You choose which Claude roles it applies to.
Note: Pendo also supports managed authorization that uses your identity provider, such as Okta, as the identity source. If you use this option, you don't need to set anything up in Pendo. Follow the steps in Auto-connect your organization's apps to Claude.
How it works
Pendo matches each member to their Pendo account by email address, so members can use the Pendo MCP server in Claude without signing in to Pendo. You manage Claude auto-connect in your Claude settings and in your Pendo organization settings.
Claude confirms that each member belongs to your Claude organization. It doesn't check a sign-in at your identity provider or multi-factor authentication.
Claude auto-connect uses each member's existing Pendo permissions, so members can only access the data they could access by signing in to Pendo directly.
Terms used in this article
The following terms are used across Claude and Pendo:
- Managed authorization: Lets a Claude admin connect Pendo for members of their Claude organization, so members don't need to sign in or approve access.
- Claude auto-connect: Managed authorization that uses Claude as the identity source (called Claude-issued in Claude's settings), so members connect to the Pendo MCP server without signing in to Pendo.
Before you begin
Setting up Claude auto-connect for the Pendo MCP server requires the following:
- Access to Claude auto-connect for your Claude organization. Claude auto-connect is in beta and becomes generally available on November 23, 2026. During the beta, Anthropic turns on this access for you. To request it, send your Claude organization ID to your Anthropic contact. For more information, see Auto-connect your organization's apps to Claude.
- A Pendo organization admin and a Claude admin. These can be the same person or two people working together.
- SSO on your Pendo organization.
- The Pendo MCP server turned on for your subscription.
- An email address in Claude for each member that matches the email address on their Pendo account.
In Claude
The Claude admin completes these steps first, in the Pendo connector in Claude.
- Go to Admin settings > Connectors.
- Find and select the Pendo connector.
- Select the Configuration tab.
- Next to Managed authorization, select Set up.
- On the Connect step, under Identity source, select Claude-issued.
- Claude displays an Issuer URL that is unique to your organization. Copy this value. If you're not a Pendo admin, share this URL with your organization's Pendo admin.
In Pendo
As a Pendo admin, you add the issuer URL from Claude so Pendo knows to trust Claude when it signs in your members.
- Go to Settings > Organization settings.
- Select the SSO tab.
- Select MCP authorization.
- In the Claude auto-connect section, paste the issuer URL you copied from Claude into the Issuer URL field, then select Save.
- Under Tenant ID, select Copy tenant ID. This is your Pendo organization ID. If you're not the Claude admin, share it with your organization's Claude admin.
Enable managed authorization in Claude
The Claude admin finishes the connection in the Managed authorization setup for the Pendo connector.
- Paste the tenant ID you copied from Pendo into the Tenant ID field. This tells Claude which Pendo organization to connect your members to.
- Select Test connection. All checks pass when the issuer URL and the tenant ID match the values you copied from Claude and Pendo. If a check fails, confirm both values and test again.
- Confirm that the sign-in server address Claude displays matches Pendo's authorization server.
- Select Enable and continue.
- (Optional) Choose which Claude roles get managed sign-in. By default, everyone in your Claude organization does.
After you enable managed authorization, members are connected to Pendo the first time they use the Pendo MCP server in Claude, without signing in. This applies to members whose Claude email address matches their Pendo email address and whose Claude role you selected.
Tip: Before you announce the change to your organization, ask two or three members to query Pendo data in Claude and confirm that no Connect prompt appears.
Manage member access
When someone leaves your organization, remove their account in Pendo as well as in Claude. Removing them from Claude stops new sign-ins, but access Pendo has already granted lasts up to an hour. Pendo matches members by email address. If you reuse a departed member's email address for a new member, that person gains access to the previous member's Pendo account.
If a member isn't connected
Members outside the roles you selected, or whose email addresses don't match, see the Connect prompt and can sign in to Pendo directly. Check that:
- Their Claude email address matches their Pendo email address. Matching ignores letter case.
- They have a Pendo account in this organization.
- Their Claude role is one you selected for managed sign-in.
Related articles
- Overview of the Pendo MCP server. Learn what the Pendo MCP server is, what it can do, and how authentication works.
- Connect to the Pendo MCP server. Set up the connection between Pendo and your AI client.
- Auto-connect your organization's apps to Claude. Anthropic's guide to managed authorization in Claude.