← Back to directory
A

Auth0 MCP Server

Official
Manage Auth0 tenants via natural language MCP server
GitHub source repository ↗
★ 113 Stars Category · Other Very popular Source revision 10390b40dc48
62FMRS · C
Reliability
8/20
Security and permissions
15/20
Maintenance
10/20
Documentation
16/20
Setup experience
13/20

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.

Read the FMRS scoring method →

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.

Tools

auth0_list_applications
List all applications in the Auth0 tenant or search by name
auth0_get_application
Get details about a specific Auth0 application
auth0_create_application
Create a new Auth0 application
auth0_update_application
Update an existing Auth0 application
auth0_save_credentials_to_file
Save an application's credentials as environment variables to a project's .env file (and add it to .gitignore)
auth0_onboarding
Onboard a project with Auth0: creates an application configured for the given framework and saves credentials to a .env file
auth0_get_quickstart_guide
Fetch the framework quickstart prompt, resolve and update callback URLs, and return code to integrate the Auth0 SDK
auth0_list_resource_servers
List all resource servers (APIs) in the Auth0 tenant
auth0_get_resource_server
Get details about a specific Auth0 resource server
auth0_create_resource_server
Create a new Auth0 resource server (API)
auth0_update_resource_server
Update an existing Auth0 resource server
auth0_create_application_grant
Create a client grant that authorizes an Auth0 application to access a specific API with defined scopes
auth0_list_actions
List all actions in the Auth0 tenant
auth0_get_action
Get details about a specific Auth0 action
auth0_create_action
Create a new Auth0 action
auth0_update_action
Update an existing Auth0 action
auth0_deploy_action
Deploy an Auth0 action
auth0_list_logs
List logs from the Auth0 tenant
auth0_get_log
Get a specific log entry by ID
auth0_list_forms
List all forms in the Auth0 tenant
auth0_get_form
Get details about a specific Auth0 form
auth0_create_form
Create a new Auth0 form
auth0_update_form
Update an existing Auth0 form
auth0_publish_form
Publish an Auth0 form

Setup

  1. Ensure Node.js v18 or higher.
  2. For Claude Desktop, run npx @auth0/auth0-mcp-server init.
  3. For other clients, use npx @auth0/auth0-mcp-server init --client <client-name> or manually add MCP configuration.
  4. After running init, your browser will open automatically to complete the OAuth device authorization flow.
  5. 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"
      }
    }
  }
}

Fit and risk

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)

Troubleshooting

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

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 DesktopFull support
Claude CodeFull support
WindsurfFull support
cursorFull support
VS CodeFull support
Gemini CLIFull support
Codex CLIFull support