Auth0 MCP server

What the model can do

Auth0 tenant administration: find a user by email or a Lucene query and see their user id, email, name, connections, whether blocked and verified, last login and login count, their roles and recent log events (logins, failures, changes), the tenant's recent logs, organisations and their members, roles, applications and the count of active users. Never phone numbers, pictures, metadata, IPs or secrets. When asked, it can block or unblock a user, clear a brute-force lockout, sign a user out everywhere, revoke their refresh tokens, delete a user, assign or remove roles, add or remove organisation members, or invite someone to an organisation by email; each changes who can get in.

Reads

• auth0_find_usersFind Auth0 users by exact email, or by a Lucene query over user fields (e.g. blocked:true, identities.connection:"google-oauth2"…
• auth0_get_userOne Auth0 user by user_id: email, name, username, connections, whether blocked, whether verified, last login, login count, dates…
• auth0_user_logsAn Auth0 user's log events, newest first: event type code (s = successful login, f = failed login, sapi = management change …), description…
• auth0_logsThe Auth0 tenant's most recent log events, newest first: type code, description, application, connection, the user (user_id and user name) and date.
• auth0_organizationsAuth0 organisations: id, name and display name.
• auth0_organization_membersAn Auth0 organisation's members: user_id, name and email (never pictures).
• auth0_rolesAuth0 roles defined in the tenant: id, name and description.
• auth0_applicationsAuth0 applications: client id, name, type and description only (never secrets or settings).

Acts, when you ask

These change something in Auth0. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• auth0_block_userBlock an Auth0 user: they can no longer log in to any application on this tenant until unblocked.
• auth0_unblock_userUnblock an Auth0 user an administrator blocked, so they can log in again.
• auth0_clear_login_lockoutRemove the brute-force protection blocks on an Auth0 user (after too many failed logins), so they can try again.
• auth0_revoke_sessionsDelete every Auth0 session of a user, so they must log in again everywhere.
• auth0_revoke_refresh_tokensDelete all of an Auth0 user's refresh tokens, so applications can no longer renew their access without a new login.
• auth0_delete_userDelete an Auth0 user.
• auth0_assign_rolesAssign existing tenant roles to an Auth0 user, granting the permissions those roles carry in every application that reads them.
• auth0_remove_rolesRemove tenant roles from an Auth0 user, taking away the permissions they carried.
• auth0_add_organization_membersAdd existing Auth0 users to an organisation, giving them access to log in through it.
• auth0_remove_organization_membersRemove users from an Auth0 organisation, so they can no longer log in through it.
• auth0_invite_to_organizationInvite someone to an Auth0 organisation.

Connect it

First connect Auth0 on Dashboard → Connections, then add Memtro to your client once. The Auth0 tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Auth0 connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Why can't priya@acme.com log in?
• › Which users are blocked?
• › Who is a member of the BigCo organisation?
• › How many failed logins were there today?
• › Sign Dan Fletcher out everywhere and revoke his refresh tokens

Questions

Is this an official Auth0 MCP server?

No. It is Memtro's MCP server with Memtro's Auth0 connector behind it: the connector reads Auth0 through its API with the credentials you connect on Dashboard → Connections, and Auth0 publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Auth0?

Only when you ask, and only what it has been granted: block a user from logging in; unblock a user an administrator blocked; clear a user's brute-force login lockout; sign a user out of every session; revoke all of a user's refresh tokens; delete a user (permanent); assign roles to a user; remove roles from a user; add users to an organisation; remove users from an organisation; invite someone to an organisation (emails them an invitation). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server