Auth0 MCP Server

What Auth0 MCP Server does

Auth0 MCP Server MCP server exposes Auth0 tenant management operations to MCP-compatible AI clients. It lets an agent work with applications, APIs, Actions, logs, forms, and users through conversational requests rather than requiring each task to be performed in the Auth0 dashboard.

Typical requests include creating an application and returning its domain and client ID, creating and deploying an Action, searching logs for activity from a particular IP address, or onboarding a project with Auth0. The onboarding flow can create an application for a framework, write credentials to a project .env file, resolve callback URLs, update the application, and return framework-specific SDK guidance.

The software is beta. Features and APIs may change, support is limited, and the README does not recommend it for production or critical workloads.

How it works

The server runs as a Node.js package through npx, using the MCP tool protocol to communicate with clients such as Claude Desktop, Cursor, Windsurf, Claude Code, VS Code, Gemini CLI, and Codex CLI. Other MCP clients can use a manually added stdio configuration with the server's run command.

Initial authorization starts an OAuth 2.0 device authorization flow in a browser. After the user signs in and grants permissions, credentials are stored in the operating system's keychain. The Auth0 account must have sufficient permissions for the requested tenant operations.

Tool exposure can be broad or restricted. The default is all tools when no selection is supplied, while --read-only or patterns such as auth0_list_* and auth0_get_* can limit access. Specific tools can also be named, for example an application listing and retrieval pair.

Setup and configuration

Node.js 18 or later, an Auth0 account, and an MCP client are required. The package provides an initialization command for supported clients. Examples include npx @auth0/auth0-mcp-server init --client cursor, --client windsurf, --client vscode, --client claude-code, or --client gemini.

For Claude Desktop, npx @auth0/auth0-mcp-server init configures the server with all tools, while npx @auth0/auth0-mcp-server init --read-only selects the read-only mode. Cursor and VS Code also support restricted tool patterns during initialization. Claude Code asks whether configuration should apply to the user or a project; VS Code offers global or workspace scope.

For an unsupported or manually configured client, add an MCP server named auth0 that runs npx -y @auth0/auth0-mcp-server run, then restart the client. The configuration may include --tools '<pattern>' in the argument list and DEBUG=auth0-mcp for debugging. Codex uses the same server command after authorization and can receive these settings through its MCP configuration.

Tools and capabilities

The documented capabilities cover:

• Listing and finding Auth0 applications, retrieving application details, and creating applications.
• Creating and deploying Auth0 Actions.
• Managing Auth0 APIs.
• Inspecting Auth0 logs, including searches based on an IP address.
• Managing Auth0 forms and users.
• Running project onboarding that composes application creation, credential-file output, callback URL configuration, and quickstart guidance.
• Restricting available tools by wildcard pattern, explicit names, or read-only mode.

The exact tool inventory is controlled by the selected tool configuration. Auth0 MCP Server MCP server should therefore be configured with the narrowest set of operations appropriate for the client and task.

Getting started with this Auth0 MCP Server MCP server

Always refer to the official documentation for the most accurate and up-to-date information.