Auth0 MCP Server

Official

Manage Auth0 tenants via natural language MCP server

How to install ↓ Compare GitHub source repository ↗

Category: Other #57 of 230
Stars: ★ 122 Very popular
Transport: stdio (local process)
Runtime: Node.js 18+
Credentials: API key / credential required
License: MIT
Last commit: 59 days ago
Tools: 24

62FMRS · C

The Auth0 MCP Server provides an official way to connect AI assistants to Auth0 Management APIs, supporting natural language operations. It is easy to install and works with multiple MCP clients, but is in Beta and requires careful management of permissions and scopes.

Strongest · Documentation 16/20 Weakest · Reliability 8/20

Reliability

8/20

Security and permissions

15/20

Maintenance

10/20

Documentation

16/20

Setup experience

13/20

Why each score

Reliability 8/20: Evidence is limited to the README and manifest: the start path (npx ... run/init) and declared tool list are consistent, but nothing was executed. The project is in beta with 12 open issues, and no committed tests or CI workflows are present in the supplied material, so the MCP handshake, tool-list behavior, edge cases, and error handling cannot be verified. This warrants the static-calibration deduction.
Security and permissions 15/20: The docs describe credentials stored in the system keychain, OAuth 2.0 device authorization flow, no scopes by default, interactive scope selection, --read-only/--tools least-privilege filtering, redaction of sensitive fields in responses, and disclosed opt-out anonymized analytics. No red-line issues such as malware, credential theft, or covert exfiltration are visible. However, the implementation cannot be verified statically, the default tool set is all tools, and sensitive create/deploy operations have no per-invocation confirmation, so full marks are not justified.
Maintenance 10/20: MIT license, official Auth0 organization, npm package with version 0.1.0-beta.10, an issue tracker, and a responsible-disclosure channel are all present. But the supplied material contains no commit history, release cadence, or dependency-update evidence; the beta status and 12 open issues leave governance and versioning gaps that prevent a higher score.
Documentation 16/20: The README is layered and thorough: client-specific setup, authentication/session/logout, tool tables with natural-language examples, scope selection, read-only/tool-filter modes, troubleshooting, debug logging, development build steps, rate-limit and private-cloud limitations, and analytics disclosure. Deductions are for missing per-tool parameter schemas and cost-related guidance, and because the evidence is documentation only rather than reviewable tests or execution traces.
Setup experience 13/20: Setup is clear and short: npx init/run, ready-made configuration examples for Claude Desktop, Claude Code, Windsurf, Cursor, VS Code, Gemini CLI, Codex, and a generic JSON client, followed by browser-based device authorization. Deductions: private-cloud or restricted environments require manual client-credentials configuration, and under static calibration setup cannot exceed 15 without committed CI or tests proving the documented flow actually works.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

Developers looking to streamline Auth0 management tasks
Teams using AI assistants like Claude to accelerate Auth0 configuration
Automating Auth0 administrative operations

Not for

Production use (currently in Beta, features may change)
Private cloud tenants (device authorization flow not supported)
Scenarios requiring broad permissions without careful scope configuration

Required permissions

Requires access to Auth0 Management API, authenticated via OAuth 2.0 device authorization flow or client credentials
Supported scopes include read:clients, create:clients, update:clients, read:resource_servers, create:resource_servers, update:resource_servers, read:actions, create:actions, update:actions, read:logs, read:forms, create:forms, update:forms
Credentials are stored in the system keychain, never plain text

Risks and side effects

Server is in Beta, may have undiscovered bugs or feature changes
If misconfigured (e.g., granting too many permissions), AI assistant may inadvertently modify your Auth0 tenant
API usage consumes rate limits
Logs and conversation history may contain sensitive information (though automatic redaction is present)

Setup

Before you start

Runtime：Node.js 18+

Other optional settings (4)

DEBUG optional Debug flag; set to auth0-mcp to enable detailed logging for troubleshooting connection and authentication issues.

AUTH0_MCP_READ_ONLY optional Set to true as an equivalent of the --read-only flag to enable only read tools, for environments where CLI flags cannot be passed.

AUTH0_MCP_TOOLS optional Equivalent of the --tools flag; a comma-separated glob pattern limiting available tools, e.g. auth0_list_*,auth0_get_*.

AUTH0_MCP_ANALYTICS optional Set to false to opt out of anonymized analytics collection (version, OS, etc.).

Ensure Node.js v18 or higher.
For Claude Desktop, run npx @auth0/auth0-mcp-server init.
For other clients, use npx @auth0/auth0-mcp-server init --client <client-name> or manually add MCP configuration.
After running init, your browser will open automatically to complete the OAuth device authorization flow.
Restart your MCP client (e.g., Claude Desktop) to load the server.

claude_desktop_config.json

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

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add auth0 -e DEBUG=auth0-mcp -- npx -y @auth0/auth0-mcp-server run

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Run npx @auth0/auth0-mcp-server init to complete the OAuth device authorization flow, restart your MCP client, then ask 'Show me all my Auth0 applications' — a returned application list confirms the connection works.

Troubleshooting

If authentication fails, re-run `npx @auth0/auth0-mcp-server init`
Check if the server is running: `ps aux | grep auth0-mcp`
Enable debug mode: `export DEBUG=auth0-mcp`
Check session status: `npx @auth0/auth0-mcp-server session`
If configuration is invalid, reinitialize or update the token

Things to try

Once connected, you can ask your AI assistant things like:

Show me all my Auth0 applications
Find applications with 'api' in their name
Create a new single-page application called 'Analytics Dashboard'
Show me failed logins from the past 24 hours

Tools 24

auth0_list_applications read-only

List all applications in the Auth0 tenant or search by name

auth0_get_application read-only

Get details about a specific Auth0 application

auth0_create_application writes

Create a new Auth0 application

auth0_update_application writes

Update an existing Auth0 application

auth0_save_credentials_to_file writes

Save an application's credentials as environment variables to a project's .env file (and add it to .gitignore)

auth0_onboarding writes

Onboard a project with Auth0: creates an application configured for the given framework and saves credentials to a .env file

auth0_get_quickstart_guide read-only

Fetch the framework quickstart prompt, resolve and update callback URLs, and return code to integrate the Auth0 SDK

auth0_list_resource_servers read-only

List all resource servers (APIs) in the Auth0 tenant

Show 16 more tools

auth0_get_resource_server read-only

Get details about a specific Auth0 resource server

auth0_create_resource_server writes

Create a new Auth0 resource server (API)

auth0_update_resource_server writes

Update an existing Auth0 resource server

auth0_create_application_grant writes

Create a client grant that authorizes an Auth0 application to access a specific API with defined scopes

auth0_list_actions read-only

List all actions in the Auth0 tenant

auth0_get_action read-only

Get details about a specific Auth0 action

auth0_create_action writes

Create a new Auth0 action

auth0_update_action writes

Update an existing Auth0 action

auth0_deploy_action writes

Deploy an Auth0 action

auth0_list_logs read-only

List logs from the Auth0 tenant

auth0_get_log read-only

Get a specific log entry by ID

auth0_list_forms read-only

List all forms in the Auth0 tenant

auth0_get_form read-only

Get details about a specific Auth0 form

auth0_create_form writes

Create a new Auth0 form

auth0_update_form writes

Update an existing Auth0 form

auth0_publish_form writes

Publish an Auth0 form

Use cases

Create and manage Auth0 applications via natural language

Deploy and update Auth0 Actions

Query and debug Auth0 logs

Quickly onboard new projects with Auth0 integration

Manage resource servers and client grants

Supported clients

Claude Desktop

Claude Code

Windsurf

Cursor

VS Code

Gemini CLI

Codex

Listed from the project's documentation, not tested by this site.

Overview

The Auth0 MCP Server connects LLMs and AI agents to Auth0 Management APIs, allowing you to create apps, deploy Actions, query logs, and manage users using natural language. It authenticates via OAuth 2.0 device authorization flow and stores credentials securely.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 509 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.6k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 654 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 579 · Tools 14 Compare with this →

Compare with other MCP servers

Source revision 10390b40dc48 Data synced 2026-10-12 Read the FMRS scoring method