Auth0 MCP Server
Auth0 tenant management via LLM agents for app, action, and user configuration tasks.
Data last scanned today · Reviewed today
Overview
The Auth0 MCP Server allows developers to interact with their Auth0 environment using natural language through MCP-compatible clients like Claude Desktop, Cursor, or Windsurf. By integrating directly into your AI workflow, it facilitates tasks such as creating new applications, managing Auth0 Actions, and inspecting log entries without requiring manual navigation of the web dashboard. Built on TypeScript, the server streamlines common administrative operations. Users can instruct their AI assistants to retrieve client credentials, deploy custom authentication logic, or troubleshoot login anomalies directly from their development environment.
Our verdict
With a security score of 45/100, this tool is classified as high risk and is currently in beta. Because critical areas such as OAuth support and read-only modes have not yet been editorially reviewed, this server should only be used in non-production, sandboxed environments. Developers should exercise caution as the software is provided as-is without warranties.
- Supports direct management of Auth0 apps and logs
- Streamlines deployment of Auth0 Actions via natural language
- Small footprint with only 11 direct dependencies
- Active repository with 18 documented contributors
- Explicitly marked as beta software
- OAuth support and security mechanisms lack editorial review
- Read-only capabilities have not been independently verified
Setup
{
"mcpServers": {
"auth0-mcp-server": {
"args": [
"-y",
"@auth0/auth0-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| auth0_list_applications | List all applications in the Auth0 tenant or search by name | low |
| auth0_get_application | Get details about a specific Auth0 application | low |
| auth0_create_application | Create a new Auth0 application | medium |
| auth0_update_application | Update an existing Auth0 application | medium |
| auth0_save_credentials_to_file | Save an application's credentials as environment variables to a project's .env file (and add it to .gitignore) | medium |
| auth0_onboarding | Onboard a project with Auth0: creates an application configured for the given framework and saves credentials to a .env file | medium |
| auth0_get_quickstart_guide | Fetch the framework quickstart prompt, resolve and update callback URLs, and return code to integrate the Auth0 SDK | low |
| auth0_list_resource_servers | List all resource servers (APIs) in the Auth0 tenant | low |
| auth0_get_resource_server | Get details about a specific Auth0 resource server | low |
| auth0_create_resource_server | Create a new Auth0 resource server (API) | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Is the Auth0 MCP server suitable for production use?
No, this software is currently in beta and is not recommended for production use or critical workloads.
›What software prerequisites are required to run this server?
You need Node.js v18 or higher, an Auth0 account with the appropriate permissions, and an MCP-compatible client like Claude Desktop, Cursor, or Windsurf.
›Can I limit the tools available to the AI?
Yes, you can use the --tools parameter to specify specific tools or use the --read-only flag to restrict access to read-only operations.
›What is the difference between User and Project configuration scopes?
The User scope is written to a global configuration file and is available across all projects, while the Project scope is written to a local .mcp.json file intended for repository sharing.
›Does the server support manual configuration for clients not explicitly listed?
Yes, you can manually add the server to any MCP client by using the command 'npx -y @auth0/auth0-mcp-server run' in your client's configuration file.
Changelog
- Securityv0.1.0-beta.17
2026-07-21
- Newv0.1.0-beta.16
2026-06-29
- Fixv0.1.0-beta.15
2026-06-17
- Securityv0.1.0-beta.14
2026-06-10
- Fixv0.1.0-beta.13
2026-05-21
- Newv0.1.0-beta.12
2026-05-05
- Newv0.1.0-beta.11
2026-04-13
- Securityv0.1.0-beta.10
2026-03-26
- Securityv0.1.0-beta.9
2026-03-10
- Newv0.1.0-beta.8
2026-02-04
Badge
Maintain this server? Add the live badge to your README.