local-only server
The server can only run on the client’s local machine because it depends on local resources.
Integrations
Enables management of Auth0 resources through natural language, including creating and updating applications, resource servers (APIs), actions, forms, and accessing Auth0 logs. Allows performing operations like creating new Auth0 apps, deploying actions, and checking authentication logs.
📚 Documentation • 🚀 Getting Started • 💻 Supported Tools • 💬 Feedback
MCP (Model Context Protocol) is an open protocol introduced by Anthropic that standardizes how large language models communicate with external tools, resources or remote services.
⚠ Beta Feature Notice: This feature is currently in Beta. Please use with caution when calling tools, as functionality may be unstable or subject to change.
The Auth0 MCP Server integrates with LLMs and AI agents, allowing you to perform various Auth0 management operations using natural language. For instance, you could simply ask Claude to perform Auth0 management operations:
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
Prerequisites:
- Node.js v18 or higher
- Claude Desktop or any other MCP Client
- Auth0 account with appropriate permissions
Install the Auth0 MCP Server
Install Auth0 MCP Server and configure it to work with your preferred MCP client. The --tools parameter specifies which tools should be available (defaults to * if not provided).
Claude Desktop with all tools
Claude Desktop with read-only tools
Windsurf
Cursor
With limited tools access
Other MCP Clients
To use Auth0 MCP Server with any other MCP Client, you can manually add this configuration to the client and restart for changes to take effect:
You can add --tools '<pattern>' to the args array to control which tools are available. See Security Best Practices for recommended patterns.
Authenticate with Auth0
Your browser will automatically open to initiate the OAuth 2.0 device authorization flow. Log into your Auth0 account and grant the requested permissions.
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
Restart your MCP Client(Claude, Windsurf, Cursor, etc...) and ask it to help you manage your Auth0 tenant
🛠️ Supported Tools
The Auth0 MCP Server provides the following tools for Claude to interact with your Auth0 tenant:
Applications
| Tool | Description | Usage Examples |
|---|---|---|
auth0_list_applications | List all applications in the Auth0 tenant or search by name | - Show me all my Auth0 applications - Find applications with 'api' in their name - What applications do I have in my Auth0 tenant? |
auth0_get_application | Get details about a specific Auth0 application | - Show me details for the application called 'Customer Portal' - Get information about my application with client ID abc123 - What are the callback URLs for my 'Mobile App'? |
auth0_create_application | Create a new Auth0 application | - Create a new single-page application called 'Analytics Dashboard' - Set up a new native mobile app called 'iOS Client' - Create a machine-to-machine application for our background service |
auth0_update_application | Update an existing Auth0 application | - Update the callback URLs for my 'Web App' to include https://staging.example.com/callback - Change the logout URL for the 'Customer Portal' - Add development environment metadata to my 'Admin Dashboard' application |
Resource Servers
| Tool | Description | Usage Examples |
|---|---|---|
auth0_list_resource_servers | List all resource servers (APIs) in the Auth0 tenant | - Show me all the APIs in my Auth0 tenant - List my resource servers - What APIs have I configured in Auth0? |
auth0_get_resource_server | Get details about a specific Auth0 resource server | - Show me details for the 'User API' - What scopes are defined for my 'Payment API'? - Get information about the resource server with identifier https://api.example.com" |
auth0_create_resource_server | Create a new Auth0 resource server (API) | - Create a new API called 'Inventory API' with read and write scopes - Set up a resource server for our customer data API - Create an API with the identifier https://orders.example.com" |
auth0_update_resource_server | Update an existing Auth0 resource server | - Add an 'admin' scope to the 'User API' - Update the token lifetime for my 'Payment API' to 1 hour - Change the signing algorithm for my API to RS256 |
Actions
| Tool | Description | Usage Examples |
|---|---|---|
auth0_list_actions | List all actions in the Auth0 tenant | - Show me all my Auth0 actions - What actions do I have configured? - List the actions in my tenant |
auth0_get_action | Get details about a specific Auth0 action | - Show me the code for my 'Enrich User Profile' action - Get details about my login flow action - What does my 'Add Custom Claims' action do? |
auth0_create_action | Create a new Auth0 action | - Create an action that adds user roles to tokens - Set up an action to log failed login attempts - Create a post-login action that checks user location |
auth0_update_action | Update an existing Auth0 action | - Update my 'Add Custom Claims' action to include department information - Modify the IP filtering logic in my security action - Fix the bug in my user enrichment action |
auth0_deploy_action | Deploy an Auth0 action | - Deploy my 'Add Custom Claims' action to production - Make my new security action live - Deploy the updated user enrichment action |
Logs
| Tool | Description | Usage Examples |
|---|---|---|
auth0_list_logs | List logs from the Auth0 tenant | - Show me recent login attempts - Find failed logins from the past 24 hours - Get authentication logs from yesterday - Show me successful logins for user john@example.com |
auth0_get_log | Get a specific log entry by ID | - Show me details for log entry abc123 - Get more information about this failed login attempt - What caused this authentication error? |
Forms
| Tool | Description | Usage Examples |
|---|---|---|
auth0_list_forms | List all forms in the Auth0 tenant | - Show me all my Auth0 forms - What login forms do I have configured? - List the custom forms in my tenant |
auth0_get_form | Get details about a specific Auth0 form | - Show me the details of my 'Corporate Login' form - What does my password reset form look like? - Get the configuration for my signup form |
auth0_create_form | Create a new Auth0 form | - Create a new login form with our company branding - Set up a custom signup form that collects department information - Create a password reset form with our logo |
auth0_update_form | Update an existing Auth0 form | - Update the colors on our login form to match our new brand guidelines - Add a privacy policy link to our signup form - Change the logo on our password reset form |
auth0_publish_form | Publish an Auth0 form | - Publish my updated login form - Make the new signup form live - Deploy the password reset form to production |
🔒 Security Best Practices for Tool Access
When configuring the Auth0 MCP Server, it's important to follow security best practices by limiting tool access based on your specific needs. The server provides flexible configuration options that let you control which tools AI assistants can access.
You can easily restrict tool access using the --tools flag when starting the server:
This approach offers several important benefits:
- Enhanced Security: By limiting available tools to only what's needed, you reduce the potential attack surface and prevent unintended modifications to your Auth0 tenant.
- Better Performance: Providing fewer tools to AI assistants actually improves performance. When models have access to many tools, they use more of their context window to reason about which tools to use. With a focused set of tools, you'll get faster and more relevant responses.
- Resource-Based Access Control: You can configure different instances of the MCP server with different tool sets based on specific needs - development environments might need full access, while production environments could be limited to read operations only.
- Simplified Auditing: With limited tools, it's easier to track which operations were performed through the AI assistant.
For most use cases, start with the minimum set of tools needed and add more only when required. This follows the principle of least privilege - a fundamental security best practice.
🕸️ Architecture
The Auth0 MCP Server implements the Model Context Protocol, allowing Claude to:
- Request a list of available Auth0 tools
- Call specific tools with parameters
- Receive structured responses from the Auth0 Management API
The server handles authentication, request validation, and secure communication with 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
The Auth0 MCP Server uses the Auth0 Management API and requires authentication to access your Auth0 tenant.
Initial Setup
To authenticate the MCP Server:
This will start the device authorization flow, allowing you to log in to your Auth0 account and select the tenant you want to use.
Important
The init command needs to be run whenever:
- You're setting up the MCP Server for the first time
- You've logged out from a previous session
- You want to switch to a different tenant
- Your token has expired
Session Management
To see information about your current authentication session:
Logging Out
For security best practices, always use the logout command when you're done with a session:
This ensures your authentication tokens are properly removed from the system keychain.
Authentication Flow
The server uses OAuth 2.0 device authorization flow for secure authentication with Auth0. Your credentials are stored securely in your system's keychain and are never exposed in plain text.
🩺 Troubleshooting
When encountering issues with the Auth0 MCP Server, several troubleshooting options are available to help diagnose and resolve problems.
Start troubleshooting by exploring all available commands and options:
🚥 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
The server provides an interactive scope selection interface during initialization:
- 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:Copy
Note
Selected scopes determine what operations the MCP server can perform on your Auth0 tenant.
⚙️ Configuration
Other MCP Clients:
To use Auth0 MCP Server with any other MCP Client, you can add this configuration to the client and restart for changes to take effect:
Note
You can manually update if needed or if any unexpected errors occur during the npx init command.
🚨 Common Issues
- Authentication Failures
- Ensure you have the correct permissions in your Auth0 tenant
- Try re-initializing with
npx @auth0/auth0-mcp-server init
- Claude Can't Connect to the Server
- Restart Claude Desktop after installation
- Check that the server is running with
ps aux | grep auth0-mcp
- API Errors or Permission Issues
- Enable debug mode with
export DEBUG=auth0-mcp - Check your Auth0 token permissions and expiration
- Reinitialize with specific scopes:
npx @auth0/auth0-mcp-server init --scopes 'read:*,update:*,create:*' - If a specific operation fails, you may be missing the required scope
- Enable debug mode with
Tip
Most connection issues can be resolved by restarting both the server and Claude Desktop.
📋 Debug logs
Enable debug mode to view detailed logs:
Get detailed MCP Client logs from Claude Desktop:
For advanced troubleshooting, use the MCP Inspector:
For detailed MCP Server logs, run the server in debug mode:
👨💻 Development
Building from Source
Note
This server requires Node.js v18 or higher.
🔒 Security
The Auth0 MCP Server prioritizes 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
logoutcommand when no longer needed
Important
For security best practices, always use npx @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.
Anonymized Analytics Disclosure
Anonymized data points are collected during the use of this MCP server. This data includes the MCP version, operating system, timestamp, and other technical details that do not personally identify you.
Auth0 uses this data to better understand the usage of this tool to prioritize the features, enhancements and fixes that matter most to our users.
To opt-out of this collection, set the AUTH0_MCP_ANALYTICS environment variable to false.
💬 Feedback and Contributing
We appreciate feedback and contributions to this project! Before you get started, please see:
Reporting Issues
To provide feedback or report a bug, please raise an issue on our issue tracker.
Vulnerability Reporting
Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.
📄 License
This project is licensed under the MIT license. See the LICENSE file for more info.
What is Auth0?
This server cannot be installed
The Auth0 MCP Server integrates with LLMs and AI agents, allowing you to perform various Auth0 management operations using natural language. For instance, you could simply ask Claude to "Create a new Auth0 app and get the domain and client ID"