Repository navigation
Conversation
Add a page explaining how Claude and Mixpanel admins connect Claude to the Mixpanel MCP Server for a whole organization, with Claude or Okta as the issuer. Nest it under the MCP Server page in the sidebar and link it from the Claude connection instructions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
 [Low impact] The PR appears safe to merge. Reviews (11) · Last reviewed commit: "Update docs/mcp/claude-enterprise-manage..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ed-auth Updates the nav entry and the MCP page's link, and redirects /mcp/claude-enterprise-managed-auth to the new path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each MCP connection, interactive or enterprise-managed, writes an mcp_client.authorized entry to every organization the member belongs to. Only disconnecting is still unrecorded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| * **Claude as the issuer:** remove them from your Claude organization. | ||
| * **Okta as the issuer:** remove them from Okta, or unassign them from the Mixpanel MCP app. | ||
|
|
||
| If you use directory sync (SCIM), Claude removes a member when your directory deletes them, but not when it only suspends them or marks them inactive. |
There was a problem hiding this comment.
This seems to be describing Claude's SCIM integration rather than Mixpanel? Is this relevant?
| | Check | Usual cause | What to do | | ||
| | - | - | - | | ||
| | **Check eligibility** | This organization or connector can't use Claude as the issuer. | Contact Claude support, or set up with Okta. | | ||
| | **Discover authorization server** | Mixpanel didn't publish its sign-in details. | Contact Mixpanel support. | |
There was a problem hiding this comment.
| | **Discover authorization server** | Mixpanel didn't publish its sign-in details. | Contact Mixpanel support. | | |
| | **Discover authorization server** | Mixpanel's sign-in details are unavailable. | Contact Mixpanel support. | |
|
|
||
| 1. **Create the Mixpanel MCP app (Okta admin)** | ||
|
|
||
| Mixpanel isn't in Okta's app catalog with Cross App Access (XAA), Okta's feature that lets one app reach another app on a user's behalf without a separate sign-in or consent screen. Instead, create a custom app integration using either OIDC or SAML 2.0. See [Okta's guide to creating an app integration](https://developer.okta.com/docs/guides/create-an-app-integration/openidconnect/main/). Use the values in the Okta tables above. |
There was a problem hiding this comment.
Mixpanel isn't in Okta's app catalog with Cross App Access (XAA), Okta's feature that lets one app reach another app on a user's behalf without a separate sign-in or consent screen.
Do we have plans to get this in place that we can mention it in the FAQ section?
There was a problem hiding this comment.
good call out! will add that
|
|
||
| ## Set up with Okta as the issuer | ||
|
|
||
| ### Settings |
There was a problem hiding this comment.
The settings should probably follow the step where they're required, rather than being presented without context up front.
Does it matter which they're using (OIDC vs SAML)? If OIDC is easier and changes nothing for the setup, we should probably just point people that way until XAA is enabled on the official mixpanel app.
| | Setting | Value | | ||
| | - | - | | ||
| | **Single sign-on URL** | `https://mixpanel.com/` | | ||
| | **Audience URI (SP Entity ID)** | `https://auth.mixpanel.com` | |
There was a problem hiding this comment.
More concretely re: OIDC vs SAML -- we provide explicit Mixpanel app setup instructions here: https://docs.mixpanel.com/docs/access-security/single-sign-on/okta#configure-saml -- these values shouldn't impact EMA MCP auth + the ones provided here won't work for login.
If someone is already using a custom app, they can add the XAA config there, rather than making a new app basically.
This reverts commit 872cb10.
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
To be deployed on November 2
Before: The docs had no page on enterprise-managed connections. That is the setup where admins connect Claude to the Mixpanel MCP Server for a whole organization, so members don't each sign in and approve the connection. The content existed only in an internal Notion draft.
After: A new page,
/docs/mcp/claude-enterprise-managed-auth, covers:The MCP Server page's Claude section links to it.
How:
docs/mcp/claude-enterprise-managed-auth.mdx.docs.json, "MCP Server" is now a group withdocs/mcpas its main page, so/docs/mcpkeeps its URL. This follows the "MCP Connections" group's layout.docs/mcp.mdxlinks to the new page.mint broken-linkspasses.Notes for reviewers:
🤖 Generated with Claude Code