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.8656 npmMIT
- 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.56 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.784 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.984 npm13MIT
TDQS
Scored across 32 tools
Most tools are clearly distinct by resource and dimension (e.g., login stats by client/hour vs. IP, user vs. client vs. session stats). Some overlap exists in event retrieval (get_events, get_admin_events, get_password_update_events) and session inspection, but the detailed descriptions help an agent differentiate them.
Names predominantly follow a consistent snake_case verb_noun pattern (get_*, list_*, reset_*, set_*, search_*). A few report-style tools (daily_brief, spray_check, health_check) deviate from strict verb_noun, but casing and readability remain consistent.
32 tools is excessive for a single MCP server; many event and statistics tools (e.g., get_login_stats, get_login_stats_by_client, get_login_stats_by_hour, get_login_failures_by_ip) could be consolidated via parameters. This volume increases navigation overhead and cognitive load for an agent.
The server covers security monitoring and containment well (events, stats, disable user, logout, password reset) but lacks core administrative CRUD operations like create/delete user, group membership management, client/role creation, and clearing brute-force lockouts. These are notable gaps for a Keycloak admin surface.