Auth0
Manage an Auth0 tenant — users, roles, organizations, connections, applications and the tenant log — through the Management API.
About
Auth0 ships in the w6w first-party pack. It declares 18 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.auth0- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Security & Identity · Developer Tools
Overview
Auth0 is an identity platform, and this app manages a tenant’s users, roles, organizations, connections, and applications through its Management API — the pieces a workflow needs to touch when someone joins, changes teams, or leaves. It creates, looks up, and updates users; assigns and revokes roles at the tenant or organization level; adds people to B2B organizations; and reads the connections and applications a tenant has configured.
A few capabilities go further than a bare CRUD wrapper. Offboarding can block a user instead of deleting them, preserving the audit trail and revocable access that a permanent delete throws away. Inviting someone who doesn’t have an account yet works through a one-time password-setup link, creating the user only once they use it — useful for provisioning flows that shouldn’t leave half-made accounts behind if an invitation is ignored. Reading the tenant’s authentication log supports the reliable, no-gaps pagination Auth0 recommends for a recurring job, rather than the ordinary paging that stops working past a thousand entries.
Build with Auth0
Three routes to the same 18 actions. The Workflow tab is generated from Auth0's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List applications
client-list The tenant's applications and their types. Client secrets are deliberately excluded from the request, not just from the output.
List connections
connection-list The tenant's identity sources and their strategies. Only an `auth0`-strategy connection can have users created in it.
List tenant logs
log-list Logins, failures and admin changes. Use checkpoint paging (`from` + `take`) for anything recurring — ordinary paging stops at 1,000 entries.
List organizations
organization-list The tenant's organizations — Auth0's B2B unit, each with its own members, branding and enabled sign-in connections.
Add members to an organization
organization-member-add Add existing users to an organization. Membership alone grants nothing — roles inside the organization are a separate step.
List organization members
organization-member-list Members of one organization, optionally with their roles inside it — which are separate from any tenant-level roles they hold.
Create a password-change ticket
password-change-ticket Mint a one-time URL for a user to set their own password — so the workflow never handles one. Treat the URL itself as a secret.
List roles
role-list The tenant's roles and their `rol_…` ids — the lookup every role assignment needs, since ids differ between tenants and names do not.
Create user
user-create Create a user in a database connection. Only database connections can be written to — a Google or SAML identity lives at the provider, not here.
Delete user
user-delete Permanently delete a user. Blocking is usually what an offboarding workflow wants: this frees the email for a new signup and does not revoke live tokens.
Get user
user-get One user by id — immediately consistent, unlike search. The id's prefix names the connection they signed up through.
Get users by email
user-get-by-email Find users by email address, immediately consistent. Returns an ARRAY — the same address in two connections is two users, and picking the first is picking arbitrarily.
Search users
user-list Lucene search over the tenant's users. Eventually consistent and capped at 1,000 results — use Get User or Get User By Email when either matters.
Assign roles to a user
user-role-assign Grant tenant-level roles by id. Additive and safe to re-run — existing roles are left alone.
List a user's roles
user-role-list Roles assigned directly to a user at the tenant level. Roles granted inside an organization are separate and do not appear here.
Remove roles from a user
user-role-remove Revoke tenant-level roles by id, leaving their other roles alone. Worth doing before blocking, so an unblock does not restore access.
Update or block user
user-update Change a user's profile or metadata, or block them from signing in. Blocking is the reversible alternative to deleting, and keeps the audit trail.
Send a verification email
verification-email-send Queue Auth0's address-verification email. It returns a JOB — pending, not delivered — and uses the tenant's own template.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Auth0's real ids.
{
"manifestVersion": "2",
"name": "auth0-example",
"steps": [
{
"id": "organization-member-add",
"uses": {
"app": "io.w6w.auth0",
"action": "organization-member-add",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"organizationId": "<organizationId>",
"userIds": "<userIds>"
}
}
]
}Here are some of the things you can do
-
Add members to an organization
performorganization-member-add -
List applications
readclient-list -
List connections
readconnection-list -
List tenant logs
readlog-list -
List organizations
readorganization-list
+13 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Auth0, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Auth0. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "organization-member-add",
payload: {
organizationId: "<value>",
userIds: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action organization-member-add --payload '{"organizationId":"<value>","userIds":"<value>"}'Give an AI agent Auth0 — without giving it Auth0's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.auth0#organization-member-add",
"input": {
"organizationId": "<organizationId>",
"userIds": "<userIds>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Auth0 connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Auth0's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Auth0 itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Auth0 declares its own checks, so its health is a property of the app rather than something the host guesses at.
Auth0 platform status
Tenant reachability
Reads one user from this connection's own tenant — catching a renamed tenant, a revoked Management API grant, and a token that was never refreshed.