Enterprise-Managed Auth for Amplitude MCP
ONew for Amplitude MCP: enterprise admins can manage Claude access through their company’s identity provider instead of asking each user to authorize a separate OAuth connection. People connect using their existing identity, while Amplitude applies their permissions. This makes it easier for IT to govern and revoke AI access without slowing teams down.
What it is
What it is: New for Amplitude MCP, org admins can let people connect Claude through their company’s identity provider instead of each person authorizing a separate OAuth connection. Amplitude applies each person’s existing permissions.
Why: IT can centrally govern who connects and what access Claude receives, while employees avoid individual consent prompts. Other MCP clients continue to use OAuth or service accounts.
Who it is for: IT administrators, identity and access management teams, and security leaders who govern AI access; plus product, analytics, and engineering teams using Claude with Amplitude.
What customers get: Centrally managed access through their identity provider. Access limited by the person’s Amplitude permissions and allowed scopes, with an option to cap a connector at read-only. A connection tied to an existing person, not a shared bot identity.
How to set it up: Org admins: In Amplitude, go to Settings → MCP → Cross App Access → Add identity provider. Members: Connect Claude to mcp.amplitude.com/mcp.