- > Create a new Auth0 app and get the domain and client ID
- > Create and deploy a new Auth0 action to generate a JWT token
- > Could you check Auth0 logs for logins from 192.108.92.3 IP address?
Getting Started
- Claude Desktop or any other MCP Client
- Auth0 account with appropriate permissions
Install the Auth0 MCP Server
Authenticate with Auth0
[!NOTE] Credentials are securely stored in your system's keychain. You can optionally verify storage through your keychain management tool. Checkout Authentication for more info.
Verify your integration
Supported Tools
Applications
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Resource Servers
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Actions
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Logs
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Forms
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Architecture
- Request a list of available Auth0 tools
- Call specific tools with parameters
- Receive structured responses from the Auth0 Management API
[!NOTE] The server operates as a local process that connects to Claude Desktop, enabling secure communication without exposing your Auth0 credentials.
Authentication
Initial Setup
[!IMPORTANT] Theinit
command needs to be run whenever:
Session Management
Logging Out
Authentication Flow
Troubleshooting
Operation Modes
Debug Mode
- More detailed logging
- Enable by setting environment variable:
export DEBUG=auth0-mcp
[!TIP] Debug mode is particularly useful when troubleshooting connection or authentication issues.
Scope Selection
- Interactive Selection: Navigate with arrow keys and toggle selections with spacebar
- No Default Scopes: By default, no scopes are selected for maximum security
- Glob Pattern Support: Quickly select multiple related scopes with patterns:
[!NOTE] Selected scopes determine what operations the MCP server can perform on your Auth0 tenant.
Configuration
Other MCP Clients:
[!NOTE]you can manually update if needed or if any unexpected errors occur during the npx init command.
Common Issues
- Authentication Failures
- Claude Can't Connect to the Server
- API Errors or Permission Issues
[!TIP] Most connection issues can be resolved by restarting both the server and Claude Desktop.
Debug logs
Development
Building from Source
[!NOTE] This server requires Node.js v18 or higher.
Security
- Credentials are stored in the system's secure keychain
- No sensitive information is stored in plain text
- Authentication uses OAuth 2.0 device authorization flow
- No permissions (scopes) are requested by default
- Interactive scope selection allows you to choose exactly which permissions to grant
- Support for glob patterns to quickly select related scopes (e.g.,
read:*
)
- Easy token removal via
logout
command when no longer needed
[!IMPORTANT] For security best practices, always usenpx @auth0/auth0-mcp-server logout
when you're done with a session or switching between tenants. This ensures your authentication tokens are properly removed from the system keychain.
[!CAUTION] Always review the permissions requested during the authentication process to ensure they align with your security requirements.
Feedback and Contributing
Reporting Issues
Vulnerability Reporting
License
What is Auth0?
- > Create a new Auth0 app and get the domain and client ID
- > Create and deploy a new Auth0 action to generate a JWT token
- > Could you check Auth0 logs for logins from 192.108.92.3 IP address?
Getting Started
- Claude Desktop or any other MCP Client
- Auth0 account with appropriate permissions
Install the Auth0 MCP Server
Authenticate with Auth0
[!NOTE] Credentials are securely stored in your system's keychain. You can optionally verify storage through your keychain management tool. Checkout Authentication for more info.
Verify your integration
Supported Tools
Applications
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Resource Servers
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Actions
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Logs
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Forms
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Architecture
- Request a list of available Auth0 tools
- Call specific tools with parameters
- Receive structured responses from the Auth0 Management API
[!NOTE] The server operates as a local process that connects to Claude Desktop, enabling secure communication without exposing your Auth0 credentials.
Authentication
Initial Setup
[!IMPORTANT] Theinit
command needs to be run whenever:
Session Management
Logging Out
Authentication Flow
Troubleshooting
Operation Modes
Debug Mode
- More detailed logging
- Enable by setting environment variable:
export DEBUG=auth0-mcp
[!TIP] Debug mode is particularly useful when troubleshooting connection or authentication issues.
Scope Selection
- Interactive Selection: Navigate with arrow keys and toggle selections with spacebar
- No Default Scopes: By default, no scopes are selected for maximum security
- Glob Pattern Support: Quickly select multiple related scopes with patterns:
[!NOTE] Selected scopes determine what operations the MCP server can perform on your Auth0 tenant.
Configuration
Other MCP Clients:
[!NOTE]you can manually update if needed or if any unexpected errors occur during the npx init command.
Common Issues
- Authentication Failures
- Claude Can't Connect to the Server
- API Errors or Permission Issues
[!TIP] Most connection issues can be resolved by restarting both the server and Claude Desktop.
Debug logs
Development
Building from Source
[!NOTE] This server requires Node.js v18 or higher.
Security
- Credentials are stored in the system's secure keychain
- No sensitive information is stored in plain text
- Authentication uses OAuth 2.0 device authorization flow
- No permissions (scopes) are requested by default
- Interactive scope selection allows you to choose exactly which permissions to grant
- Support for glob patterns to quickly select related scopes (e.g.,
read:*
)
- Easy token removal via
logout
command when no longer needed
[!IMPORTANT] For security best practices, always usenpx @auth0/auth0-mcp-server logout
when you're done with a session or switching between tenants. This ensures your authentication tokens are properly removed from the system keychain.
[!CAUTION] Always review the permissions requested during the authentication process to ensure they align with your security requirements.