Auth0 MCP Server

The Auth0 MCP Server connects your agent to your Auth0 tenant through the Auth0 Management API. You manage applications, APIs, Actions, forms and logs in plain words instead of in the dashboard. Auth0 marks it as beta. What you can do with it - List, create and update applications, and save an app's credentials to your project's .env file - Create and update APIs (resource servers) and their scopes, and grant an application access to an API - Write, update and deploy Actions - Search your tenant's logs, such as failed logins or logins from one IP address - Create and update forms How it connects It runs on your machine with npx -y @auth0/auth0-mcp-server run. Auth0 documents setup for Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Gemini CLI and Codex, and it also installs as a Gemini CLI extension. Signing in Run npx @auth0/auth0-mcp-server init once before first use. It opens your browser to sign in to Auth0 (OAuth 2.0 device authorization), lets you choose the tenant and the permissions (scopes) to grant, and keeps the token in your system keychain. Run init again to switch tenants or when the token expires, and npx @auth0/auth0-mcp-server logout when you're done. Read-only when you want it Add --read-only to the run command to offer only its list and get tools, or choose tools with --tools (for example 'auth0_list_*,auth0_get_*'). Good to know - It replaces secrets such as client secrets and tokens with [REDACTED] in its replies. - It uses your tenant's Management API rate limits. - Auth0 collects anonymized usage data; set AUTH0_MCP_ANALYTICS=false to opt out. - Private Cloud tenants sign in with client credentials instead of the browser flow.