Auth0 MCP Server for Claude

Content

Auth0 MCP Server is Auth0's official local Model Context Protocol server for connecting Claude and other MCP-capable clients to Auth0 tenant administration workflows. It runs through the @auth0/auth0-mcp-server npm package, uses Auth0 authentication, and exposes Management API tools according to the scopes and tool filters you grant during setup.

The best first use is read-only tenant inspection: list applications, inspect API resource servers, retrieve Actions, and review authentication logs before drafting a change. After you have reviewed the exact tools and scopes, the same server can assist with controlled create, update, deploy, and publish workflows for Auth0 resources.

Features

• Official Auth0 documentation page for setup, authentication, client support, tool access controls, and troubleshooting.
• Public auth0/auth0-mcp-server source repository with an MIT license.
• Published npm package at @auth0/auth0-mcp-server.
• Local stdio MCP server that can be configured for Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, and other compatible clients.
• OAuth 2.0 device authorization setup for standard Auth0 tenants.
• Client-credentials setup path for private cloud tenants and other non-interactive cases.
• Read-only mode through --read-only or AUTH0_MCP_READ_ONLY=true.
• Tool filtering with glob patterns through --tools or AUTH0_MCP_TOOLS.
• Documented Management API scope selection during initialization.
• System keychain credential storage, logout command, and redaction of sensitive fields in tool responses.
• Optional analytics opt-out with AUTH0_MCP_ANALYTICS=false.

Tool Surface

Auth0 documents tools for these resource groups:

• Applications: list, inspect, create, and update Auth0 applications.
• Resource servers: list, inspect, create, and update APIs and scopes.
• Application grants: create grants between applications and APIs.
• Actions: list, inspect, create, update, and deploy Actions.
• Logs: list recent tenant logs and retrieve a specific log event.
• Forms: list, inspect, create, update, and publish forms.

Use read-only mode when your task is investigation, support triage, onboarding, or documentation. Move to mutating tools only when the tenant, scope set, and approval path are explicit.

Installation

Auth0 Initialization

Configure the Auth0 MCP Server with the safest starter mode:

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

For a narrower read-only tool set, use Auth0's documented tool filters:

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

The initialization flow opens a browser for Auth0 authorization and lets you select the tenant and scopes. Restart your MCP client after setup.

MCP Client Config

Use this stdio configuration when manually configuring a compatible client:

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

To enable a limited non-read-only surface, replace --read-only with a specific tool pattern and matching scopes. For example, a development-tenant workflow for applications might use --tools 'auth0_*_application*' only after the selected tenant and permissions are approved.

Use Cases

• Ask Claude to list Auth0 applications and summarize callback URL drift before changing a web app configuration.
• Review recent failed login logs, blocked attempts, or tenant errors while debugging an authentication incident.
• Inspect resource server scopes before drafting an API authorization update.
• Retrieve an Action's current code and ask Claude to explain what it changes in the login or token flow.
• Create or update a development tenant application after confirming redirect URLs, allowed origins, token settings, and ownership.
• Draft a new Action in a non-production tenant, review the code manually, then approve deployment only after tests pass.
• Compare form configuration or branding across tenants before publishing a change.

Safety Checklist

• Use a development tenant for first-time setup and mutating workflows.
• Prefer --read-only until the task genuinely requires create, update, deploy, or publish tools.
• Grant only the Auth0 Management API scopes required for the current task.
• Confirm the selected tenant before approving tool calls.
• Keep MCP client approval prompts enabled for every mutating operation.
• Do not expose Auth0 secrets or production user records in prompts.
• Run npx @auth0/auth0-mcp-server session to check the active tenant and authentication state when unsure.
• Run npx @auth0/auth0-mcp-server logout after temporary administration work.

Source Links

• Auth0 documentation: https://auth0.com/docs/get-started/auth0-mcp-server
• Source repository: https://github.com/auth0/auth0-mcp-server
• npm package: https://www.npmjs.com/package/@auth0/auth0-mcp-server
• MCP specification: https://modelcontextprotocol.io/specification/2025-06-18/