Skip to content

MCP setupSecurity

Auth0 MCP Server

Inspect Auth0 applications, APIs, actions and logs from your coding agent with Auth0's official MCP server, in read-only mode by default.

npx workspacetemplates add auth0-mcp --tool claude-code

Writes 1 file to your project root

.mcp.jsonmerge into your file16 lines · 261 BFile
{
  "mcpServers": {
    "auth0": {
      "command": "npx",
      "args": [
        "-y",
        "@auth0/auth0-mcp-server",
        "run",
        "--read-only"
      ],
      "env": {
        "AUTH0_MCP_ANALYTICS": "${AUTH0_MCP_ANALYTICS}"
      }
    }
  }
}

What it does

Auth0 ships this server to manage a tenant from chat. Its tools list and read applications, resource servers, actions, forms and logs, and can also create and update them when you allow it.

Setup has two parts. Run npx @auth0/auth0-mcp-server init once to sign in with the browser device flow and choose a tenant; the credentials go into your system keychain. Then the agent starts the server with the run command.

This config adds --read-only, so the agent can inspect the tenant but not change it. Remove the flag only when you want writes.

Example

you › List the last 20 failed login events and group them by error type.

agent › Pulled 20 log entries. 12 are wrong password, 5 are blocked by an action, 3 are an expired link. The 5 blocked ones all came from the same application.

Questions

How do I sign in?
Run npx @auth0/auth0-mcp-server init in a terminal. It opens a browser for the device authorization flow, and you pick the tenant and scopes there.
Can I limit which tools are available?
Yes. The flag --tools takes patterns such as auth0_list_*,auth0_get_*. If you pass both that and --read-only, read-only wins.
Does it work with a private cloud tenant?
Device flow does not. Initialize with an M2M app using the --auth0-domain, --auth0-client-id and --auth0-client-secret options instead.
  • CSRF and CORS Hardening

    SkillSecurity

    Free