Skip to main content
Glama
mgcrea

@mgcrea/mcp-keycloak

by mgcrea

Related Servers

Alternatives to @mgcrea/mcp-keycloak

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      Enables management of Keycloak identity and access management through the Keycloak Admin REST API, providing 299 tools for operations like user management, client configuration, and realm administration via natural language.
      100
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients and JavaScript callers to administer Keycloak realms through the Keycloak Admin REST API using OAuth 2.0 client credentials, with searchable operation discovery, read-only calls, and guarded workflow execution for mutations.
      93 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Keycloak admin operations as tools via the Model Context Protocol, allowing management of users, clients, groups, roles, and more through natural language.
      93 npm
      MIT
    • A
      license
      A
      quality
      B
      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
      75 npm
      2
      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
      59 npm
      MIT
    • 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.
      59 npm
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 44 tools

    Disambiguation5/5

    Each tool maps to a distinct Keycloak resource and action, and the list/get/count/evaluate distinctions are consistently clear. Even the two diagnostic tools differ: auth_status covers configuration readiness while whoami reports effective admin roles.

    Naming Consistency5/5

    Every tool follows the keycloak_<verb>_<resource> snake_case convention, with verbs mostly limited to list, get, count, and evaluate. The few one-offs like auth_status, whoami, and request are conventional and do not break the overall pattern.

    Tool Count2/5

    At 44 tools, this is a very heavy surface for an agent to hold in context, even though each tool maps to a legitimate Keycloak endpoint. The count exceeds the point where a tool set feels curated and starts to resemble a reference dump.

    Completeness3/5

    Read-side coverage is broad, including users, groups, roles, clients, scopes, sessions, events, flows, and identity providers. However, curated create/update/delete operations are almost entirely absent for core resources, and the keycloak_request escape hatch is the only path for writes and advanced features like credentials or authorization.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues