Zitadel MCP
Related Servers
Alternatives to Zitadel MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables centralized authentication and authorization for MCP servers, with OAuth 2.1, static API keys, and JWT verification via drop-in middleware.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude, Cursor, VS Code, and other MCP clients to connect to your tools by signing in with ZapQR via passkey or phone scan, with per-person identity verified on every request. It implements OAuth 2.1 resource-server discovery, 401 challenges, and JWT validation so tools can run without passwords, API keys, or a user table.MIT
- AlicenseNot gradedqualityFmaintenanceAdd authentication to your app without leaving your IDE. Creates projects, configures auth methods, wires up OAuth, and scaffolds sign-in flows - all from your editor's chat.35 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables remote MCP server connections with WorkOS AuthKit authentication and user management. Supports organization-centric authentication and permission-based tool access control.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to connect to Authentik and securely query users, groups, applications, events, and system status, with an optional gated tool to enable or disable user accounts.MIT
- AlicenseBqualityBmaintenanceEnables agents and apps to verify end-user identity through company API keys, human login links with multi-channel notifications, OIDC client registration, and budget-aware billing.131MIT
TDQS
Scored across 34 tools
Tools are mostly distinct: user lifecycle, grants, org managers, projects, apps, and translations each have clear boundaries. The only mild overlap is between composite helpers (provision_user, offboard_user) and their constituent low-level operations, but descriptions make the intended use clear.
All tools use the zitadel_ prefix with snake_case verb_noun naming (e.g. zitadel_list_users, zitadel_create_user_grant, zitadel_grant_org_manager). Conventions are consistent across the entire set.
34 tools is above the 25-tool threshold for 'too many' in the rubric; while Zitadel is broad, the surface feels heavy and includes several composite wrappers alongside granular operations.
User lifecycle is complete (create, list, get, deactivate, reactivate, lock, unlock, delete), and grants/managers are well covered. However, projects and apps lack update/delete operations, login policy is read-only, and service-user keys have no delete/revoke, leaving notable gaps.