Skip to main content
Glama
keycloak-mcp

keycloak-mcp

by shigechika

Related Servers

Alternatives to keycloak-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides a natural language interface for managing Keycloak identity and access management through its REST API.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      A 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.
      86
      39 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      8
      74 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets an AI assistant inspect and modify Keycloak realm, client, and protocol-mapper configuration across multiple Keycloak hosts.
      7
      102 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      9
      102 npm
      13
      MIT

    TDQS

    A3.9/5.0

    Scored across 33 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data