Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Auth0 MCP Server

by auth0version 0.1.0-beta.10i★ –iRuns on your computer
Registry namecom.auth0/mcp

Install

Overview

Description from the maker (original English)

Auth0 MCP Server: Manage Auth0 applications, APIs, actions, logs, and forms using natural language

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "auth0": {
      "command": "npx",
      "args": [
        "-y",
        "@auth0/auth0-mcp-server",
        "run"
      ]
    }
  }
}

Run this in your terminal

claude mcp add auth0 -- npx -y @auth0/auth0-mcp-server run

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "auth0": {
      "command": "npx",
      "args": [
        "-y",
        "@auth0/auth0-mcp-server",
        "run"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "auth0": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@auth0/auth0-mcp-server",
        "run"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain auth0.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32455 servers in this category
  • Published to the registry more recently than 5% of the other 32455 servers in this category
  • Basic checks equal to or better than 100% of the other 32455 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Auth0 MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0-beta.10) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SSTracker free youth training

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

📚 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.

Connect Claude, Cursor, or Windsurf to your Auth0 tenant to create apps, deploy Actions, debug logs, and manage users — all without touching the dashboard.

[!CAUTION]

Beta Software Notice: This software is currently in beta and is provided AS IS without any warranties.

- Features, APIs, and functionality may change at any time without notice

- Not recommended for production use or critical workloads

- Support during the beta period is limited

- Issues and feedback can be reported through the GitHub issue tracker

By using this beta software, you acknowledge and accept these conditions.

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 Desktop 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:

Install the Auth0 MCP Server

Install Auth0 MCP Server and configure it to work with your preferred MCP Client. The --tools parameter specifies which tools should be available (defaults to * if not provided).

Claude Desktop with all tools

npx @auth0/auth0-mcp-server init

Claude Desktop with read-only tools

npx @auth0/auth0-mcp-server init --read-only

You can also explicitly select read-only tools:

npx @auth0/auth0-mcp-server init --tools 'auth0_list_*,auth0_get_*'

Claude Code

Initialize the Auth0 MCP server for Claude Code

npx @auth0/auth0-mcp-server init --client claude-code

You will be prompted to choose a configuration scope:

  • User — written to ~/.claude.json and available across all your projects.
  • Project — written to .mcp.json at a project folder you specify, intended to be checked into version control and shared with your team.

Windsurf

npx @auth0/auth0-mcp-server init --client windsurf

Cursor

Step 1:

Step 2:

npx @auth0/auth0-mcp-server init --client cursor

Cursor with limited tools access

npx @auth0/auth0-mcp-server init --client cursor --tools 'auth0_list_applications,auth0_get_application'

VS Code

npx @auth0/auth0-mcp-server init --client vscode

You can configure VS Code for either global or workspace scope:

  • Global: Available in all VS Code instances
  • Workspace: Available only in a specific project/repository

The command will prompt you to choose your preferred scope and automatically configure the appropriate mcp.json file.

VS Code with limited tools access

npx @auth0/auth0-mcp-server init --client vscode --tools 'auth0_list_*,auth0_get_*' --read-only

Gemini CLI

Initialize the gemini MCP server for the Gemini CLI

npx @auth0/auth0-mcp-server init --client gemini

Install the Gemini Extension

gemini extensions install https://github.com/auth0/auth0-mcp-server

Codex CLI

Authenticate once with Auth0:

npx @auth0/auth0-mcp-server init

Then add the Auth0 MCP server to Codex:

codex mcp add auth0 --env DEBUG=auth0-mcp --env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus -- npx -y @auth0/auth0-mcp-server run

You can also add it directly to ~/.codex/config.toml:

[mcp_servers.auth0]

command = "npx" args = ["-y", "@auth0/auth0-mcp-server", "run"]

[mcp_servers.auth0.env] DEBUG = "auth0-mcp" DBUS_SESSION_BUS_ADDRESS = "unix:path=/run/user/1000/bus"

Restart Codex after updating the configuration.

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:

{

"mcpServers": { "auth0": { "command": "npx", "args": ["-y", "@auth0/auth0-mcp-server", "run"], "capabilities": ["tools"], "env": { "DEBUG": "auth0-mcp" } } } }

You can add --tools ' ' to the args array to control which tools are available. See Security Best Practices for recommended patterns.

Authorize 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. Check out Authentication for more info.

Verify your integration

Restart your MCP Client (Claude Desktop, Windsurf, Cursor, etc.) and ask it to help you manage your Auth0 tenant

Onboard your project

To get a project running with Auth0 from scratch, ask your MCP Client to onboard it (e.g. Onboard my Next.js project with Auth0). This invokes the auth0_onboarding tool, which creates an Auth0 application configured for your framework and writes the credentials to a .env file in your project. Under the hood it composes the auth0_create_application and auth0_save_credentials_to_file tools to do this. It then hands off to auth0_get_quickstart_guide, which resolves your callback URLs, updates the application, and returns the framework-specific code to integrate the Auth0 SDK — taking you from no Auth0 setup to a working integration in a single guided flow.

🛠️ Supported Tools

The Auth0 MCP Server provides the following tools for Claude to interact with your Auth0 tenant:

Applications
ToolDescriptionUsage Examples

| auth0_list_applications | List all applications in the Auth0 tenant or search by name | - Show me all my Auth0 applications

  • Find applications with 'api' in their name
  • What applications do I have in my Auth0 tenant? |

| auth0_get_application | Get details about a specific Auth0 application | - Show me details for the application called 'Customer Portal'

  • Get information about my application with client ID abc123
  • What are the callback URLs for my 'Mobile App'? |

| auth0_create_application | Create a new Auth0 application | - Create a new single-page application called 'Analytics Dashboard'

  • Set up a new native mobile app called 'iOS Client'
  • Create a machine-to-machine application for our background service |

| auth0_update_application | Update an existing Auth0 application | - Update the callback URLs for my 'Web App' to include https://staging.example.com/callback

  • Change the logout URL for the 'Customer Portal'
  • Add development environment metadata to my 'Admin Dashboard' 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) | - Save my app's Auth0 credentials to a .env file in this project

  • Write the client ID and secret for 'Web App' to .env.local
  • Store these Auth0 credentials in my project's environment file |
Onboarding
ToolDescriptionUsage Examples

| auth0_onboarding | Onboard a project with Auth0: creates an application configured for the given framework and saves credentials to a .env file | - Onboard my Next.js project with Auth0

  • Set up Auth0 for my React app in this directory
  • Get my Express app started with Auth0 |

| auth0_get_quickstart_guide | Fetch the framework quickstart prompt, resolve and update callback URLs, and return code to integrate the Auth0 SDK | - Show me how to add the Auth0 SDK to my Next.js app

  • Complete the Auth0 integration for my project
  • Give me the quickstart code for my React application |
Resource Servers

| Tool | Description | Usage Examples

Only the beginning is shown; read the rest in the repo

Ask PopNx