Zitadel MCP Server

An MCP (Model Context Protocol) server for Zitadel identity management. Manage users, projects, applications, roles, and service accounts through natural language from AI tools like Claude Code.

"Provision jane@example.com as an Admin." — One tool call: creates the user, assigns the admin project role (v2 authorization), and grants ORG_USER_MANAGER so she can manage other users — no Super Admin required.

Tools (33)

Portal tools (portal_*) are only available when PORTAL_DATABASE_URL is configured.

Two-role model & no-super-admin (Renewal Initiatives SSO)

The provisioning tools implement a standardized RBAC model for the core apps:

• Two project (business) roles only: admin and standard — these land in the OIDC token and gate what a user can do in the apps. The provisioning tools refuse any other key to prevent drift.
• No Super Admin: every Admin also receives an org-level ORG_USER_MANAGER grant (a manager role — administers Zitadel itself, not in the token), so any Admin can create/manage any user, including other Admins. Keep ≥2 ORG_OWNER break-glass accounts for org configuration.
• Role assignment prefers the v2 AuthorizationService (POST /v2/authorizations) and automatically falls back to v1 user-grants if that endpoint is unavailable on the instance (some Zitadel Cloud versions return 404). Org-manager grants use the Management v1 org-member API.

Prerequisites

1. A Zitadel instance (Cloud or self-hosted)
2. A service account with Org Owner or IAM Admin role
3. A JSON key for the service account

Creating a Service Account

1. In the Zitadel Console, go to Users > Service Users > New
2. Give it a name (e.g., mcp-admin) and select Bearer token type
3. Go to the service user's Keys tab > New > JSON
4. Save the downloaded key file — you'll need the userId, keyId, and base64-encoded key
5. Grant the service account the Org Owner role under Organization > Authorizations

Setup

git clone https://github.com/takleb3rry/zitadel-mcp.git

cd zitadel-mcp

npm install

npm run build

Configuration

Add the server to your MCP client config. The JSON block below works for both options:

• Global (all projects): ~/.claude.json under the "mcpServers" key
• Per-project: .mcp.json in the project root

{

  "mcpServers": {

    "zitadel": {

      "command": "node",

      "args": ["/path/to/zitadel-mcp/build/index.js"],

      "env": {

        "ZITADEL_ISSUER": "https://your-instance.zitadel.cloud",

        "ZITADEL_SERVICE_ACCOUNT_USER_ID": "...",

        "ZITADEL_SERVICE_ACCOUNT_KEY_ID": "...",

        "ZITADEL_SERVICE_ACCOUNT_PRIVATE_KEY": "...",

        "ZITADEL_ORG_ID": "...",

        "ZITADEL_PROJECT_ID": "..."

      }

    }

  }

}

Restart Claude Code after adding the config. The Zitadel tools will appear automatically.

Environment Variables

Security

This server has admin-level access to your Zitadel instance. Understand what that means before using it:

• The service account needs org-level management rights. Empirically (Zitadel Cloud, verified 2026-06): ORG_USER_MANAGER is enough to create users and assign existing project roles, but ORG_OWNER is required to create project roles, manage org-manager grants (the no-super-admin pattern), and manage applications. For the full provisioning workload, give the service account ORG_OWNER; human Admins can stay at ORG_USER_MANAGER. Keep the key in a gitignored .env (not a shared dotfile) and use ZITADEL_READ_ONLY=true for non-mutating sessions.
• When you create an OIDC app (zitadel_create_oidc_app), the client secret is returned in the tool response. It is only available at creation time. The AI assistant (and its conversation history) will see it — save it immediately and treat it as sensitive.
• When you generate a service account key (zitadel_create_service_user_key), the full private key is returned in the tool response. Same caveat: save it, and be aware it's visible in your MCP client's conversation.
• All tool arguments containing PII (email, name, URLs) are redacted from debug logs. IDs and tool names are still logged.
• All Zitadel IDs are validated against an alphanumeric format before being used in API paths.

Note for new users: I've scanned all source files in this repo and found nothing notable, but I always recommend you have your own AI or tooling audit the code before installing any MCP server that gets access to your infrastructure. The full source is ~800 lines of TypeScript — a quick review shouldn't take long.

Development

npm run dev    # Run with tsx (hot reload)

npm run build  # Compile TypeScript

npm start      # Run compiled version

npm test       # Run tests

License

MIT