- Home
- MCP servers
- Zitadel
Zitadel
- typescript
0
GitHub Stars
typescript
Language
3 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"takleb3rry-zitadel-mcp": {
"command": "node",
"args": [
"/path/to/zitadel-mcp/build/index.js"
],
"env": {
"ZITADEL_ISSUER": "https://your-instance.zitadel.cloud",
"ZITADEL_ORG_ID": "...",
"ZITADEL_PROJECT_ID": "...",
"ZITADEL_SERVICE_ACCOUNT_KEY_ID": "...",
"ZITADEL_SERVICE_ACCOUNT_USER_ID": "...",
"ZITADEL_SERVICE_ACCOUNT_PRIVATE_KEY": "..."
}
}
}
}You use the Zitadel MCP Server to manage identities, projects, applications, roles, and service accounts in Zitadel through natural-language style tool calls. This enables AI-assisted workflows that can, for example, create a user, assign a role, and retrieve authentication configuration in a single integrated process.
How to use
You interact with the Zitadel MCP Server by calling its tools through an MCP client. These tools cover users, projects, applications, roles, service accounts, and organizational information. You can perform common administration tasks such as creating users, inviting them to projects, creating applications, granting roles, generating service keys, and obtaining authentication configuration templates.
How to install
Prerequisites: you need a Zitadel instance (cloud or self-hosted), a service account with Org Owner or IAM Admin privileges, and a JSON key for the service account.
Step-by-step setup flow includes cloning the MCP server repository, installing dependencies, and building the server. Follow these commands exactly to prepare and run the MCP server locally.
Configuration and usage notes
The MCP server exposes a set of tools you can call from your MCP client. The configuration example below shows how to run the MCP server locally using Node and point it at a built index. You must provide the required environment variables to authenticate and authorize actions against your Zitadel instance.
Security and best practices
This server has admin-level access to your Zitadel instance. Ensure you protect the service account credentials and treat generated keys as highly sensitive. Review access controls, redact sensitive details in logs, and rotate keys and tokens according to your security policy.
Available tools
zitadel_list_users
List or search Zitadel users.
zitadel_get_user
Retrieve detailed information for a specific user.
zitadel_create_user
Create a new user (sends an invitation email).
zitadel_deactivate_user
Deactivate a user account.
zitadel_reactivate_user
Reactivate a previously deactivated user.
zitadel_list_projects
List projects in the organization.
zitadel_get_project
Get details for a specific project.
zitadel_create_project
Create a new project.
zitadel_list_apps
List applications within a project.
zitadel_get_app
Get application details plus Client ID.
zitadel_create_oidc_app
Create an OpenID Connect application.
zitadel_update_app
Update application settings (redirect URIs, etc.).
zitadel_list_project_roles
List roles defined in a project.
zitadel_create_project_role
Create a new project role (e.g., app:finance).
zitadel_list_user_grants
List roles granted to a user.
zitadel_create_user_grant
Assign roles to a user.
zitadel_remove_user_grant
Remove a user’s role grant.
zitadel_create_service_user
Create a machine/service account user.
zitadel_create_service_user_key
Generate a key pair for a service user.
zitadel_list_service_user_keys
List keys for a service user (metadata only).
zitadel_get_org
Get current organization details.
zitadel_list_orgs
List organizations.
zitadel_get_auth_config
Get the .env.local template for an app.
portal_register_app
Register an app in the portal database.
portal_setup_full_app
One-click setup for Zitadel and portal integration.