Auth0 MCP Server – Tenant Management Tools

Overview

Auth0's official MCP Server connects MCP-compatible AI clients to an Auth0
tenant through the Auth0 Management API. It is designed for secure, local use
from tools such as Claude Desktop, Claude Code, Cursor, Windsurf, VS Code,
Gemini CLI, Codex, and other clients that can launch a stdio MCP process.

What the MCP server enables

Auth0 MCP exposes tenant-management tools that can be restricted by tool
patterns, read-only mode, and selected Auth0 scopes. Depending on the granted
permissions, an AI agent can:

• List, inspect, create, and update Auth0 applications.
• List, inspect, create, and update resource servers and API scopes.
• List, inspect, create, and update Auth0 Actions.
• Query Auth0 logs and investigate login or operational events.
• Work with supported Auth0 forms operations.
• Create and save generated Auth0 application credentials to a local file when
  explicitly requested.
• Help implement API authorization flows and security-monitoring workflows using
  tenant data.

When to use it

Use Auth0 MCP when an AI agent should help administer or inspect an Auth0 tenant
during development and operations. Practical examples include creating a new
single-page application, reviewing callback URLs, creating a machine-to-machine
client, defining an API resource server and scopes, deploying an Action,
checking failed login logs, or generating an authorization setup plan from the
current tenant configuration.

Connection and authentication

The server is installed and run with the official npm package. For most clients,
initialize the integration with npx @auth0/auth0-mcp-server init, then run the
server with npx -y @auth0/auth0-mcp-server run. Node.js v18 or higher is
required.

The default authentication flow uses OAuth 2.0 device authorization. The browser
opens for the user to log in, choose a tenant, and grant scopes. Credentials are
stored in the system keychain. Private cloud tenants can authenticate with
client credentials by providing Auth0 domain, client ID, and client secret
during initialization. The server also supports session and logout commands
for checking or clearing local credentials.

Key considerations

Auth0 documents the server as beta software. No scopes are requested by default;
users choose scopes during initialization, and selected scopes determine which
tenant operations are allowed. Use --read-only or --tools patterns to limit
the MCP tool surface, especially in shared or production environments. Auth0
Management API rate limits apply, and every operation should be treated as a
real tenant change when write tools are enabled. Review requested permissions,
prefer least privilege, keep client credentials short-lived for private cloud
usage, and run logout when switching tenants or ending a session. Anonymous
analytics can be disabled by setting AUTH0_MCP_ANALYTICS=false.