Auth0 Mcp Server

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.

[!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_*'

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

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

🛠️ Supported Tools

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

Applications

Resource Servers

Application Grants

Actions

Logs

Forms

🔒 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 and --read-only flags when starting the server:

# Enable only read-only operations
npx @auth0/auth0-mcp-server run --read-only

# Alternative way to enable only read-only operations
npx @auth0/auth0-mcp-server run --tools 'auth0_list_*,auth0_get_*'

# Limit to just application-related tools
npx @auth0/auth0-mcp-server run --tools 'auth0_*_application*'

# Limit to read-only application-related tools
# Note: --read-only takes priority when used with --tools
npx @auth0/auth0-mcp-server run --tools 'auth0_*_application*' --read-only

# Restrict to only log viewing capabilities
npx @auth0/auth0-mcp-server run --tools 'auth0_list_logs,auth0_get_log'

# Run the server with all tools enabled
npx @auth0/auth0-mcp-server run --tools '*'

[!IMPORTANT]

When both --read-only and --tools flags are used together, the --read-only flag takes priority for security. This means even if your --tools pattern matches non-read-only tools, only read-only operations will be available. This ensures you can rely on the --read-only flag as a security guardrail.

This approach offers several important benefits:

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

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

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

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

🛡️ Credential Protection

The server automatically redacts sensitive fields (e.g., client_secret, token etc.) in relevant MCP tool responses, replacing them with [REDACTED]. This prevents secrets from leaking into AI assistant logs or conversation history.

To securely store credentials locally, the auth0_save_credentials_to_file tool writes Auth0 credentials as environment variables to a user-specified file (e.g., .env.local), and automatically adds it to .gitignore. If the file already exists, credentials are appended (preserving existing content); otherwise, a new file is created. This tool can be invoked manually or the AI assistant will automatically prompt you to save credentials after creating an application.

🧪 Security Scanning

We recommend regularly scanning this server, and any other MCP-compatible servers you deploy, with community tools built to surface protocol-level risks and misconfigurations.

These scanners help identify issues across key vulnerability classes including: server implementation bugs, tool definition and lifecycle risks, interaction and data flow weaknesses, and configuration or environment gaps.

Useful tools include:

• **mcpscan.ai**

Web-based scanner that inspects live MCP endpoints for exposed tools, schema enforcement gaps, and other issues.

• **mcp-scan**

CLI tool that simulates attack paths and evaluates server behavior from a client perspective.

These tools are not a substitute for a full audit, but they offer meaningful guardrails and early warnings. We suggest including them in your regular security review process.

If you discover a vulnerability, please follow our responsible disclosure process.

🕸️ Architecture

The Auth0 MCP Server implements the Model Context Protocol, allowing Claude to:

1. Request a list of available Auth0 tools

2. Call specific tools with parameters

3. 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:

npx @auth0/auth0-mcp-server init

This will start the device authorization flow, allowing you to log in to your Auth0 account and select the tenant you want to use.

[!NOTE]

Authenticating using device authorization flow is not supported for private cloud tenants.

Private Cloud users should authenticate with client credentials.Keep the token lifetime as minimal as possible to reduce security risks. See more

```bash

npx @auth0/auth0-mcp-server init --auth0-domain