keycloak-mcp
Related Servers
Alternatives to keycloak-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides a natural language interface for managing Keycloak identity and access management through its REST API.MIT
- AlicenseCqualityDmaintenanceA 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.8639 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.39 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables 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.874 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an AI assistant inspect and modify Keycloak realm, client, and protocol-mapper configuration across multiple Keycloak hosts.7102 npmMIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables management of Keycloak users and realms through a standardized interface, providing tools for user creation, deletion, role assignment, and group management.9102 npm13MIT
TDQS
Scored across 33 tools
Most tools target a distinct resource+action (users, sessions, clients, events, config), and descriptions actively differentiate look-alikes (e.g. get_ip_activity vs get_events, get_admin_events vs get_events). The only soft overlap is among the IP-centric investigation tools (get_login_failures_by_ip, get_ip_activity, spray_check) and the several login-stat variants, but descriptions make the boundaries navigable.
Nearly all tools follow a consistent get_/list_/search_/reset_/set_ verb_noun snake_case pattern (get_user, list_clients, reset_passwords_batch, search_users). The few noun-forward names (health_check, spray_check, daily_brief) still read as verb+noun and don't break the convention.
33 tools is above the comfortable range and feels heavy, though the domain is genuinely broad (user admin, sessions, MFA, events, security analytics, config drift, health). Each tool appears to earn its place, but the surface is crowded and some analytics tools could be consolidated behind parameters.
User lifecycle is partial: read/search/count/enable/disable/reset-password exist but there is no create_user, update_user, or delete_user, and groups/roles/clients are read-only with no create/update/delete. For an observability-plus-ops surface this is workable, but a full Keycloak admin domain has notable gaps.