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
- 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.8613 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.13 npmApache 2.0
- 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.862 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an AI assistant inspect and modify Keycloak realm, client, and protocol-mapper configuration across multiple Keycloak hosts.725 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.925 npm13MIT
TDQS
Scored across 33 tools
The large login/analytics family (get_login_stats, _by_hour, _by_client, _by_ip) and the event family (get_events, get_admin_events, get_ip_activity, spray_check) are dense, but descriptions carefully draw boundaries (e.g. get_ip_activity vs get_events(ip_address), runtime brute-force vs realm policy). Only a couple of pairs (get_user_credentials vs get_totp_users, count_users vs search_users) sit close enough to risk occasional misselection.
Strong, predictable verb_noun pattern throughout (get_user, list_clients, reset_password, set_user_enabled, search_users), with iterative breakdowns forming a tidy get_login_stats_by_X series. The only deviations are noun-phrase tools with no verb prefix (health_check, daily_brief, spray_check), which is a minor, readable exception.
At 33 tools this sits above the comfortable 3-15 band and well into the 'heavy' range. The Keycloak surface is genuinely broad (users, sessions, events, clients, realm config, security), so most tools earn their place, but the analytics cluster in particular could be consolidated.
The operational/security domain is well covered end-to-end: user lookup, password reset (single and batch), enable/disable, force logout, session/credential inspection, and rich event/admin-event/security analytics with a daily brief. Gaps remain on the write/admin side — there is no create_user, delete_user, or role/group mutation (list_realm_roles and list_user_groups are read-only) — which limits it as a full admin tool.