Skip to main content
Glama
dockndevai

mcp-keycloak

Related Servers

Alternatives to mcp-keycloak

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      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.
      18 npm
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for Keycloak Admin REST API, enabling user, group, event, and security management through service account authentication.
      30
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets an AI assistant inspect and modify Keycloak realm, client, and protocol-mapper configuration across multiple Keycloak hosts.
      7
      54 npm
      MIT
    • A
      license
      C
      quality
      C
      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
      18 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Official MCP server for Skycloak (managed Keycloak) that enables managing clusters, realms, applications, identity providers, users, themes, exports, SIEM destinations, and webhooks through natural language, with OAuth or API key authentication.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables administrators to manage Keycloak realms, users, roles, clients, groups, and more through its Admin REST API, with safe-by-default configuration and destructive operation confirmation.
      56
      35 npm
      1
      MIT

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: get_realm vs list_realms, list_users vs get_user vs count_users, and list_clients/list_realm_roles/list_groups all have separate scopes. Descriptions make the boundaries explicit, so an agent should not confuse them.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun pattern: get_realm, list_users, get_user, count_users, list_clients, list_realm_roles, list_groups, list_realms. There are no mixed conventions or vague verbs.

    Tool Count5/5

    The server exposes 8 tools, which is well-scoped for a focused Keycloak read/inspection surface. No tool feels redundant, and the count avoids both bloat and a thin single-tool interface.

    Completeness2/5

    The surface is read-only and omits all create, update, and delete operations for realms, users, clients, roles, and groups. Even read coverage is incomplete, since there is no get_client, get_group, or get_role, leaving significant gaps for typical Keycloak administration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues