mcp-keycloak-admin
Related Servers
Alternatives to mcp-keycloak-admin
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables management of Keycloak identity and access management through the Keycloak Admin REST API, providing 299 tools for operations like user management, client configuration, and realm administration via natural language.1003MIT
- AlicenseAqualityAmaintenanceEnables AI agents to explore and administer a Keycloak instance via the Keycloak Admin REST API, covering realms, users, groups, roles, clients, sessions, events, client scopes, identity providers, and authentication flows, with read-only operation by default and optional write tools.4429 npmMIT
- AlicenseAqualityAmaintenanceEnables MCP-capable clients to inspect and manage Keycloak realms, users, clients, roles, and groups with layered security modes, realm allowlisting, protected realms, delete gating, dry-run, and audit logging.8506 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables administration of Keycloak identity and access management through MCP, allowing management of realms, clients, users, roles, groups, identity providers, and sessions from any MCP client.10 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes Keycloak admin operations as tools via the Model Context Protocol, allowing management of users, clients, groups, roles, and more through natural language.34 npmMIT
- AlicenseCqualityCmaintenanceA comprehensive MCP server for Keycloak administration, offering 80+ tools to manage users, realms, clients, roles, groups, sessions, events, organizations, and more directly from AI assistants.8610 npmMIT
TDQS
Scored across 56 tools
Every tool targets a distinct Keycloak resource/action combination, and the descriptions explicitly cross-reference related tools (e.g., realm vs. client roles, login vs. admin events, client scopes catalog vs. assigned scopes). Even the similar role-assignment tools are clearly separated by realm/client and user/group scope.
Tool names consistently follow the keycloak_<resource>_<verb> pattern, using predictable verbs like list, get, create, update, delete, assign, and unassign. Minor deviations such as keycloak_user_search and keycloak_server_info, plus occasional _list vs. _get for collections, prevent a perfect score.
At 56 tools, the set is far beyond the typical 3-15 tool sweet spot and crosses the 50+ threshold for an extreme count. Although the Keycloak domain is broad, this many entry points create significant agent selection overhead and suggest over-decomposition of the API surface.
User and client lifecycle CRUD is well covered, and there is broad read-only coverage of roles, scopes, mappers, auth flows, authz, and federation. However, these latter areas largely lack create/update/delete tools, and group role grants cannot be revoked (no group_role_unassign), so common admin workflows dead-end.