Auth0 MCP Server

📚 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.

Connect Claude, Cursor, or Windsurf to your Auth0 tenant to create apps, deploy Actions, debug logs, and manage users — all without touching the dashboard.

[!CAUTION]

Beta Software Notice: This software is currently in beta and is provided AS IS without any warranties.

- Features, APIs, and functionality may change at any time without notice

- Not recommended for production use or critical workloads

- Support during the beta period is limited

- Issues and feedback can be reported through the GitHub issue tracker

By using this beta software, you acknowledge and accept these conditions.

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 Desktop 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

npx @auth0/auth0-mcp-server init

Claude Desktop with read-only tools

npx @auth0/auth0-mcp-server init --read-only

You can also explicitly select read-only tools:

npx @auth0/auth0-mcp-server init --tools 'auth0_list_*,auth0_get_*'

Claude Code

Initialize the Auth0 MCP server for Claude Code

npx @auth0/auth0-mcp-server init --client claude-code

You will be prompted to choose a configuration scope:

• User — written to ~/.claude.json and available across all your projects.
• Project — written to .mcp.json at a project folder you specify, intended to be checked into version control and shared with your team.

Windsurf

npx @auth0/auth0-mcp-server init --client windsurf

Cursor

Step 1:

Step 2:

npx @auth0/auth0-mcp-server init --client cursor

Cursor with limited tools access

npx @auth0/auth0-mcp-server init --client cursor --tools 'auth0_list_applications,auth0_get_application'

VS Code

npx @auth0/auth0-mcp-server init --client vscode

You can configure VS Code for either global or workspace scope:

• Global: Available in all VS Code instances
• Workspace: Available only in a specific project/repository

The command will prompt you to choose your preferred scope and automatically configure the appropriate mcp.json file.

VS Code with limited tools access

npx @auth0/auth0-mcp-server init --client vscode --tools 'auth0_list_*,auth0_get_*' --read-only

Gemini CLI

Initialize the gemini MCP server for the Gemini CLI

npx @auth0/auth0-mcp-server init --client gemini

Install the Gemini Extension

gemini extensions install https://github.com/auth0/auth0-mcp-server

Codex CLI

Authenticate once with Auth0:

npx @auth0/auth0-mcp-server init

Then add the Auth0 MCP server to Codex:

codex mcp add auth0 --env DEBUG=auth0-mcp --env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus -- npx -y @auth0/auth0-mcp-server run

You can also add it directly to ~/.codex/config.toml:

[mcp_servers.auth0]

command = "npx" args = ["-y", "@auth0/auth0-mcp-server", "run"]

[mcp_servers.auth0.env] DEBUG = "auth0-mcp" DBUS_SESSION_BUS_ADDRESS = "unix:path=/run/user/1000/bus"

Restart Codex after updating the configuration.

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:

{

"mcpServers": { "auth0": { "command": "npx", "args": ["-y", "@auth0/auth0-mcp-server", "run"], "capabilities": ["tools"], "env": { "DEBUG": "auth0-mcp" } } } }

You can add --tools ' ' to the args array to control which tools are available. See Security Best Practices for recommended patterns.

Authorize 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. Check out Authentication for more info.

Verify your integration

Restart your MCP Client (Claude Desktop, Windsurf, Cursor, etc.) and ask it to help you manage your Auth0 tenant

Onboard your project

To get a project running with Auth0 from scratch, ask your MCP Client to onboard it (e.g. Onboard my Next.js project with Auth0). This invokes the auth0_onboarding tool, which creates an Auth0 application configured for your framework and writes the credentials to a .env file in your project. Under the hood it composes the auth0_create_application and auth0_save_credentials_to_file tools to do this. It then hands off to auth0_get_quickstart_guide, which resolves your callback URLs, updates the application, and returns the framework-specific code to integrate the Auth0 SDK — taking you from no Auth0 setup to a working integration in a single guided flow.

🛠️ Supported Tools

The Auth0 MCP Server provides the following tools for Claude to interact with your Auth0 tenant:

Applications

| 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 |

| auth0_save_credentials_to_file | Save an application's credentials as environment variables to a project's .env file (and add it to .gitignore) | - Save my app's Auth0 credentials to a .env file in this project

• Write the client ID and secret for 'Web App' to .env.local
• Store these Auth0 credentials in my project's environment file |

Onboarding

| auth0_onboarding | Onboard a project with Auth0: creates an application configured for the given framework and saves credentials to a .env file | - Onboard my Next.js project with Auth0

• Set up Auth0 for my React app in this directory
• Get my Express app started with Auth0 |

| auth0_get_quickstart_guide | Fetch the framework quickstart prompt, resolve and update callback URLs, and return code to integrate the Auth0 SDK | - Show me how to add the Auth0 SDK to my Next.js app

• Complete the Auth0 integration for my project
• Give me the quickstart code for my React application |

Resource Servers

| Tool | Description | Usage Examples