auth0.com
auth0.com logo

Auth0

Integrates with LLMs and AI agents, allowing you to perform various Auth0 management operations using natural language....

Created byApr 22, 2025
MCP server for Auth0
Documentation Getting Started Supported Tools Feedback
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.
** Beta Feature Notice:** This feature is currently in Beta. Please use with caution when calling tools, as functionality may be unstable or subject to change.
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 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:
  • Auth0 account with appropriate permissions

Install the Auth0 MCP Server

Install Auth0 MCP Server and configure it to work with your preferred MCP client.
Claude Desktop
Windsurf
Cursor
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:

Authenticate 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. Checkout Authentication for more info.

Verify your integration

Restart your MCP Client(Claude, 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

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Resource Servers

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Actions

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Logs

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Forms

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Architecture

The Auth0 MCP Server implements the Model Context Protocol, allowing Claude to:
  1. Request a list of available Auth0 tools
  1. Call specific tools with parameters
  1. 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:
This will start the device authorization flow, allowing you to log in to your Auth0 account and select the tenant you want to use.
[!IMPORTANT] The init command needs to be run whenever:

Session Management

To see information about your current authentication session:

Logging Out

For security best practices, always use the logout command when you're done with a session:
This ensures your authentication tokens are properly removed from the system keychain.

Authentication Flow

The server uses OAuth 2.0 device authorization flow for secure authentication with Auth0. Your credentials are stored securely in your system's keychain and are never exposed in plain text.

Troubleshooting

Get command line help: View a list of supported commands and usage examples

Operation Modes

Debug Mode

  • More detailed logging
  • Enable by setting environment variable: export DEBUG=auth0-mcp
[!TIP] Debug mode is particularly useful when troubleshooting connection or authentication issues.

Scope Selection

The server provides an interactive scope selection interface during initialization:
  • Interactive Selection: Navigate with arrow keys and toggle selections with spacebar
  • No Default Scopes: By default, no scopes are selected for maximum security
  • Glob Pattern Support: Quickly select multiple related scopes with patterns:
[!NOTE] Selected scopes determine what operations the MCP server can perform on your Auth0 tenant.

Configuration

Other MCP Clients:

To use Auth0 MCP Server with any other MCP Client, you can add this configuration to the client and restart for changes to take effect:
[!NOTE]you can manually update if needed or if any unexpected errors occur during the npx init command.

Common Issues

  1. Authentication Failures
  1. Claude Can't Connect to the Server
  1. API Errors or Permission Issues
[!TIP] Most connection issues can be resolved by restarting both the server and Claude Desktop.

Debug logs

Enable debug mode to view detailed logs:
Get detailed MCP Client logs from Claude Desktop:
For advanced troubleshooting, use the MCP Inspector:
For detailed MCP Server logs, run the server in debug mode:

Development

Building from Source

[!NOTE] This server requires Node.js v18 or higher.

Security

The Auth0 MCP Server prioritizes security:
  • Credentials are stored in the system's secure keychain
  • No sensitive information is stored in plain text
  • Authentication uses OAuth 2.0 device authorization flow
  • No permissions (scopes) are requested by default
  • Interactive scope selection allows you to choose exactly which permissions to grant
  • Support for glob patterns to quickly select related scopes (e.g., read:*)
  • Easy token removal via logout command when no longer needed
[!IMPORTANT] For security best practices, always use npx @auth0/auth0-mcp-server logout when you're done with a session or switching between tenants. This ensures your authentication tokens are properly removed from the system keychain.
[!CAUTION] Always review the permissions requested during the authentication process to ensure they align with your security requirements.

Feedback and Contributing

We appreciate feedback and contributions to this project! Before you get started, please see:

Reporting Issues

To provide feedback or report a bug, please raise an issue on our issue tracker.

Vulnerability Reporting

Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.

License

This project is licensed under the MIT license. See the LICENSE file for more info.

What is Auth0?

MCP server for Auth0
Documentation Getting Started Supported Tools Feedback
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.
** Beta Feature Notice:** This feature is currently in Beta. Please use with caution when calling tools, as functionality may be unstable or subject to change.
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 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:
  • Auth0 account with appropriate permissions

Install the Auth0 MCP Server

Install Auth0 MCP Server and configure it to work with your preferred MCP client.
Claude Desktop
Windsurf
Cursor
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:

Authenticate 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. Checkout Authentication for more info.

Verify your integration

Restart your MCP Client(Claude, 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

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Resource Servers

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Actions

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Logs

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Forms

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

Architecture

The Auth0 MCP Server implements the Model Context Protocol, allowing Claude to:
  1. Request a list of available Auth0 tools
  1. Call specific tools with parameters
  1. 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:
This will start the device authorization flow, allowing you to log in to your Auth0 account and select the tenant you want to use.
[!IMPORTANT] The init command needs to be run whenever:

Session Management

To see information about your current authentication session:

Logging Out

For security best practices, always use the logout command when you're done with a session:
This ensures your authentication tokens are properly removed from the system keychain.

Authentication Flow

The server uses OAuth 2.0 device authorization flow for secure authentication with Auth0. Your credentials are stored securely in your system's keychain and are never exposed in plain text.

Troubleshooting

Get command line help: View a list of supported commands and usage examples

Operation Modes

Debug Mode

  • More detailed logging
  • Enable by setting environment variable: export DEBUG=auth0-mcp
[!TIP] Debug mode is particularly useful when troubleshooting connection or authentication issues.

Scope Selection

The server provides an interactive scope selection interface during initialization:
  • Interactive Selection: Navigate with arrow keys and toggle selections with spacebar
  • No Default Scopes: By default, no scopes are selected for maximum security
  • Glob Pattern Support: Quickly select multiple related scopes with patterns:
[!NOTE] Selected scopes determine what operations the MCP server can perform on your Auth0 tenant.

Configuration

Other MCP Clients:

To use Auth0 MCP Server with any other MCP Client, you can add this configuration to the client and restart for changes to take effect:
[!NOTE]you can manually update if needed or if any unexpected errors occur during the npx init command.

Common Issues

  1. Authentication Failures
  1. Claude Can't Connect to the Server
  1. API Errors or Permission Issues
[!TIP] Most connection issues can be resolved by restarting both the server and Claude Desktop.

Debug logs

Enable debug mode to view detailed logs:
Get detailed MCP Client logs from Claude Desktop:
For advanced troubleshooting, use the MCP Inspector:
For detailed MCP Server logs, run the server in debug mode:

Development

Building from Source

[!NOTE] This server requires Node.js v18 or higher.

Security

The Auth0 MCP Server prioritizes security:
  • Credentials are stored in the system's secure keychain
  • No sensitive information is stored in plain text
  • Authentication uses OAuth 2.0 device authorization flow
  • No permissions (scopes) are requested by default
  • Interactive scope selection allows you to choose exactly which permissions to grant
  • Support for glob patterns to quickly select related scopes (e.g., read:*)
  • Easy token removal via logout command when no longer needed
[!IMPORTANT] For security best practices, always use npx @auth0/auth0-mcp-server logout when you're done with a session or switching between tenants. This ensures your authentication tokens are properly removed from the system keychain.
[!CAUTION] Always review the permissions requested during the authentication process to ensure they align with your security requirements.

Feedback and Contributing

We appreciate feedback and contributions to this project! Before you get started, please see:

Reporting Issues

To provide feedback or report a bug, please raise an issue on our issue tracker.

Vulnerability Reporting

Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.

License

This project is licensed under the MIT license. See the LICENSE file for more info.

What is Auth0?