Keycloak MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEYCLOAK_URL | Yes | Base URL of the Keycloak server | |
| KEYCLOAK_ADMIN | No | Deprecated alias still supported for password grant login | |
| KEYCLOAK_PASSWORD | No | Password for password grant login | |
| KEYCLOAK_USERNAME | No | Username for password grant login | |
| KEYCLOAK_CLIENT_ID | No | Client ID for client_credentials login (recommended) | |
| KEYCLOAK_AUTH_REALM | No | Realm where the login account or client lives | master |
| KEYCLOAK_GRANT_TYPE | No | Either client_credentials or password; detected from what you set | auto |
| KEYCLOAK_MCP_REALMS | No | Comma-separated allowlist of target realms | all |
| KEYCLOAK_MCP_TOOLSETS | No | Enabled toolsets, or all | core,groups,roles |
| KEYCLOAK_CLIENT_SECRET | No | Client secret for client_credentials login (recommended) | |
| KEYCLOAK_MCP_LOG_LEVEL | No | debug, info, warn or error (stderr) | info |
| KEYCLOAK_MCP_READ_ONLY | No | Register read-only tools only | false |
| KEYCLOAK_ADMIN_PASSWORD | No | Deprecated alias still supported for password grant login | |
| KEYCLOAK_MCP_TIMEOUT_MS | No | HTTP timeout for Keycloak requests | 30000 |
| KEYCLOAK_MCP_ALLOW_MASTER_WRITE | No | Allow write tools in the master realm | false |
| KEYCLOAK_MCP_REQUIRE_CONFIRMATION | No | Destructive and sensitive tools need confirm: true | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-userC | Create a new user in a specific realm |
| delete-userC | Delete a user from a specific realm |
| list-realmsB | List all available realms |
| list-usersC | List users in a specific realm |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: create-user and delete-user handle user lifecycle actions, list-realms lists realms, and list-users lists users within a realm. The descriptions make it unambiguous which tool to use for each operation.
All tool names follow a consistent verb_noun pattern with hyphen separation (e.g., create-user, delete-user, list-realms, list-users). This uniformity makes the tool set predictable and easy to understand.
With only 4 tools, the set feels thin for a Keycloak server, which typically manages realms, users, roles, clients, and groups. While the tools cover basic user and realm operations, the scope is limited compared to the domain's complexity.
There are significant gaps in the tool surface for Keycloak management. Missing operations include updating users, managing roles, handling clients, and performing authentication flows. This incomplete coverage will likely cause agent failures when trying to perform common administrative tasks.