$ loading_
Retrieve safe identity claims from an authenticated Auth0 access token.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "auth0-whoami-mcp" yet — see the docs or source repo.
Call who_am_i and return the safe identity claims from my current Auth0 access token in a concise list.
Returns safe identity information for the authenticated user without exposing sensitive credentials.
Use who_am_i to inspect the current Auth0 identity claims and help me verify whether the extension is running as the correct user.
Outputs a summary of identity claims useful for troubleshooting the authentication context.
Call who_am_i and tell me which Auth0 identity this MCP session is associated with, returning only safe fields.
Returns the safe Auth0 identity claims associated with the current MCP session.
Developers integrating Auth0 Custom Extensions can use it to quickly confirm which identity the current access token represents. This helps inspect the authentication context without exposing sensitive credentials.
When an MCP workflow relies on Auth0 authentication, developers or DevOps engineers can call who_am_i to inspect safe identity claims. It is useful for confirming whether the session is bound to the correct user or token context.
It is a minimal remote MCP server for Auth0 Custom Extensions. It provides a single tool, who_am_i, which returns safe identity claims from an authenticated Auth0 access token.
No. The description explicitly says it returns only safe identity claims and does not expose sensitive credentials.
The provided material does not include installation instructions. What is clear is that it is related to Auth0 Custom Extensions and an authenticated Auth0 access token; see the source repository for more details.
Enable AI agents to handle authentication, OTP verification, and token management.
Authenticate users with Auth0 and call protected APIs on their behalf.
Read Auth0 resources and configuration for fast identity environment reviews.
Add OAuth auth, scope enforcement, and delegation auditing to MCP agents.
Expose structured professional profile data so AI can answer personal background questions accurately.
Enable enterprise auth, token validation, and access control for AI agents.