Skip to content
Auth0

Auth0MCP Server

by Auth0
Added to Onei
v0.1.0-beta.17
MIT
Repository Docs npm
Developer Tools

Summary

Auth0's official MCP server: create applications, deploy Actions, inspect logs and manage users in your tenant through natural language.

Features

  • Create Auth0 applications and retrieve domain and client ID
  • Author and deploy Auth0 Actions
  • Query tenant logs, including by IP address
  • Manage users, roles and tenant resources
  • --read-only mode and glob-based tool selection via --tools
  • init subcommand configures Claude Desktop, Claude Code, Windsurf and Cursor

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Auth0" tools will be available.
{
  "mcpServers": {
    "auth0": {
      "command": "npx",
      "args": [
        "-y",
        "@auth0/auth0-mcp-server",
        "run"
      ]
    }
  }
}

Description

Auth0's official MCP server connects an agent to an Auth0 tenant, so identity work — creating applications, deploying Actions, managing users, and reading logs — happens where you are already working instead of in the dashboard.

What it is for

The operations it targets are the ones that interrupt development: standing up a new application and retrieving its domain and client ID, writing and deploying an Action, checking whether a login attempt from a specific IP succeeded, or looking up why a user is failing authentication. Each is a short dashboard round trip on its own; together they add up, and they are exactly the kind of task an agent can complete from a sentence.

Scoped access by default

The --tools flag decides which tools are exposed, and it is the important knob. npx @auth0/auth0-mcp-server init --read-only gives an agent inspection without mutation; a glob such as --tools 'auth0_list_*,auth0_get_*' selects explicitly. For a system that holds your identity provider's management credentials, starting read-only and widening deliberately is the sane default.

Client setup

An init subcommand configures the server for a specific client — Claude Desktop, Claude Code, Windsurf, and Cursor all have first-class paths. For Claude Code you choose a scope: user, written to ~/.claude.json and available across projects, or project, written to .mcp.json so it can be committed and shared with your team.

Status

The server is published under the MIT licence and is explicitly beta software, provided as-is: features and APIs may change without notice, support during the beta is limited, and Auth0 does not recommend it for production or critical workloads. Treat it as a development-time accelerator against a non-production tenant rather than something to wire into a release pipeline. Requires Node.js 18 or later.

Related MCP Servers

MCP: WorkOS

by WorkOS

WorkOS's official remote MCP server — run your WorkOS dashboard from an agent: organizations, users, SSO connections, Directory Sync, AuthKit branding and audit log streams.

Developer Tools

MCP: Clerk MCP Server

by Clerk

Clerk's official remote MCP server feeds AI coding assistants verified Clerk SDK snippets and implementation patterns, so generated auth code matches the current API.

Developer Tools
Browse all MCP servers →