CodeQL Development MCP Server
OFFICIAL SERVERWrite, test, run and profile CodeQL queries from an AI assistant through the local CodeQL CLI
Manage an Auth0 tenant's applications, APIs, Actions, forms and logs from an MCP client
Official · Auth0 TypeScript Local · stdio SecurityDeveloper tools
66 popularity score ★ 122 ↓ 12k/wk
Opens the app, which asks before it adds the server.
npx @auth0/auth0-mcp-server initclaude mcp add auth0 -- npx -y @auth0/auth0-mcp-server run{
"mcpServers": {
"auth0": {
"command": "npx",
"args": [
"-y",
"@auth0/auth0-mcp-server",
"run"
]
}
}
}{
"mcpServers": {
"auth0": {
"command": "npx",
"args": [
"-y",
"@auth0/auth0-mcp-server",
"run"
]
}
}
}{
"servers": {
"auth0": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@auth0/auth0-mcp-server",
"run"
]
}
}
}[mcp_servers.auth0]
command = "npx"
args = ["-y", "@auth0/auth0-mcp-server", "run"]gemini mcp add --scope user auth0 npx -- -y @auth0/auth0-mcp-server runAUTH0_MCP_READ_ONLY |
Optional: Set to true to expose only list and get tools; same as --read-only. |
|---|---|
AUTH0_MCP_TOOLS |
Optional: Comma-separated glob of tools to expose, e.g. auth0_list_*,auth0_get_*; same as --tools (default *). |
AUTH0_MCP_ANALYTICS |
Optional: Set to false to stop usage events being sent to Heap Analytics. |
DEBUG |
Optional: Set to auth0-mcp for detailed logging. |
Auth0's own MCP server runs on your machine and calls the Auth0 Management API for one tenant. Through it an assistant can list, inspect, create and update applications and resource servers (APIs), grant an application access to an API, write, update and deploy Actions, build and publish Forms, and read tenant logs to debug failed logins.
Two onboarding tools go further than the Management API: `auth0_onboarding` creates an application set up for a given web framework and writes its domain, client ID and secret into the project's env file (`.env.local` when none exists), and `auth0_get_quickstart_guide` returns code for adding the Auth0 SDK to a project. The server masks fields such as `client_secret` and tokens in tool responses.
Sign-in is a separate step: `npx @auth0/auth0-mcp-server init` runs the OAuth device flow in a browser, lets you pick a tenant and the Management API scopes to grant (none are selected by default), and stores the token in the system keychain; `init --client claude|claude-code|cursor|vscode|windsurf|gemini` also writes the client's config. The `run` command then starts the stdio server and checks the token first. Tool exposure can be narrowed with `--read-only` or a `--tools` glob such as `auth0_list_*,auth0_get_*`; `--read-only` wins when both are given.
Version 0.1.0-beta.19 registers 24 tools (src/tools/index.ts). Not in the README: each tool call is reported to Heap Analytics (heapanalytics.com) with the tool name, success flag, package version, OS, CPU architecture and Node version under a random per-session ID, unless `AUTH0_MCP_ANALYTICS=false` is set (src/utils/analytics.ts).
| Runtime | Node.js 18+ |
|---|
Node.js 18 or later (run through npx). An Auth0 account and tenant, signed in once with `npx @auth0/auth0-mcp-server init` (browser device flow) before the client starts the server; repeat it when the token expires or to switch tenant. An OS keychain to hold the token (on Linux a Secret Service over D-Bus; the Codex example sets DBUS_SESSION_BUS_ADDRESS). Private Cloud tenants cannot use the device flow and must run `init` with `--auth0-domain`, `--auth0-client-id` and `--auth0-client-secret` of a machine-to-machine app.
Its makers label it beta, provided as is, not recommended for production or critical workloads, with features that may change without notice. Calls count against the tenant's Management API rate limits for its subscription plan. Coverage is limited to applications, resource servers, client grants, Actions, Forms and logs: there are no tools for users, roles, connections or organizations, and no delete tools. One tenant per signed-in session. Usage analytics are on by default (see above). The MCP registry entry still points at 0.1.0-beta.10 while npm has 0.1.0-beta.19.
Suits developers who already use Auth0 and want to set up applications and APIs, edit and deploy Actions, or dig through login logs without opening the dashboard, and those onboarding a new web project who want credentials written straight into its env file. Because tools can create and deploy changes on a live tenant, point it at a development tenant or run it with `--read-only`; teams wanting a stable, supported tool for production tenants should wait for it to leave beta. It manages tenant configuration only, so it does not suit user administration.
auth0_list_applicationsauth0_get_applicationauth0_create_applicationauth0_update_applicationauth0_save_credentials_to_fileauth0_onboardingauth0_get_quickstart_guideauth0_list_resource_serversauth0_get_resource_serverauth0_create_resource_serverauth0_update_resource_serverauth0_create_application_grantauth0_list_actionsauth0_get_actionauth0_create_actionauth0_update_actionauth0_deploy_actionauth0_list_logsauth0_get_logauth0_list_formsauth0_get_formauth0_create_formauth0_update_formauth0_publish_form