Keycloak MCP Server
Provides tools for Keycloak admin operations, including managing users, clients, groups, roles, and sessions.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Keycloak MCP Server
An MCP (Model Context Protocol) server that exposes Keycloak admin operations as tools. It runs over stdio and is launched by an MCP client (Claude Desktop, Claude Code, the MCP Inspector, etc.).
It covers day-to-day administration across users, roles (including composite roles), groups,
clients, client scopes and protocol mappers, realms and realm settings, identity providers,
authentication flows, authorization services, organizations, LDAP/AD user federation, events
and realm import/export: over 100 tools in 13 groups. Load only
the groups you need with the KEYCLOAK_TOOLS environment variable.
Built on @modelcontextprotocol/sdk
and @keycloak/keycloak-admin-client.
Table of Contents
Related MCP server: Keycloak MCP Server
How it works
The server authenticates to Keycloak using the client_credentials grant (a service account) — no username/password required.
A single shared
KeycloakAdminClientis kept alive with lazy token management: the token is re-fetched only when it is within ~10s of expiry.Every tool takes a
realmargument identifying which realm the operation targets. This is distinct fromKEYCLOAK_REALM, which is only the realm used to authenticate the admin service account.Users are addressed by username, clients by clientId, groups by path or name, and roles by name — no UUIDs required in tool arguments.
All diagnostic logging goes to stderr; stdout is reserved for the MCP protocol.
Requirements
Node.js 18+ (Node 22 recommended)
A running Keycloak instance (v26.x tested)
A confidential client with a service account that has admin roles (see below)
Environment variables
Loaded from a .env file at the project root.
Variable | Required | Default | Description |
| no |
| Base URL of the Keycloak server. |
| no |
| Realm used for admin authentication (where the service-account client lives). Not the target realm of operations. |
| yes | — | The confidential client's |
| yes | — | The service account client secret. Keep this out of version control. |
| no | any location | Directory the realm import/export tools may read from and write to. When set, any other path is refused (symlinks are resolved first). Recommended. |
| no | all groups | Comma-separated tool groups to expose, e.g. |
Example .env:
KEYCLOAK_BASE_URL=http://localhost:8080
KEYCLOAK_REALM=master
KEYCLOAK_CLIENT_ID=keycloak-mcp
KEYCLOAK_CLIENT_SECRET=your-service-account-secret
KEYCLOAK_TOOLS=users,roles,groupsTool groups
With every group enabled the server exposes over 100 tools, and an MCP client loads all of
their descriptions into the model's context. KEYCLOAK_TOOLS limits that to the groups you
need. Unset, empty or all exposes everything. Names are case-insensitive; an unknown name
stops the server at startup with a message listing the valid groups.
Group | Tools |
| User read/write: profile, credentials, sessions, password, logout, impersonate, unlock. |
| Realm and client roles, role mappings on users, composite roles. |
| Groups and group membership. |
| Clients, secrets, client service-account user. |
| Client scopes, assigning them to clients, and protocol mappers (on clients and scopes). |
| Realm create/delete/enable, settings, SMTP, event-storage config. |
| Identity providers and their mappers. |
| Authentication flows, flow bindings and required actions. |
| Authorization services: resources, scopes, policies, permissions, evaluation. |
| Organizations (B2B tenants): members, invitations, linked identity providers. |
| Realm export to JSON, and import into an existing or new realm. |
| LDAP/AD user federation: providers, sync, mappers. |
| Login events and admin events. |
Each tool belongs to exactly one group. The startup line on stderr reports what was loaded,
e.g. keycloak-mcp: 32 tools registered (groups: users, roles).
A group only hides tools from the model; it is not a security boundary. What the server can actually do is still limited by the roles on the service account (see Keycloak setup). For a read-only deployment, grant only view roles.
Set it in .env, or per client in the MCP config, e.g. for Claude Code:
claude mcp add keycloak -e KEYCLOAK_TOOLS=users,roles -- <command...>⚠️ Add
.envto.gitignore. The secret is a full admin credential.
Keycloak setup (service account)
In the realm that will authenticate the server (usually
master), create a client (e.g.keycloak-mcp):Client authentication: On (confidential)
Service accounts roles: Enabled
Standard/Direct-access flows can be off.
Copy the client secret from Credentials into
KEYCLOAK_CLIENT_SECRET.Grant the service account admin roles under Service account roles:
For full access: assign the
adminrole (orrealm-adminfrom therealm-managementclient of each target realm).For read-only usage: assign roles like
view-users,view-clients,view-realm,query-users,query-clients.Write tools (create/update/delete user, reset password, assign roles, group membership, send email, logout) additionally need
manage-usersandmanage-clients.Realm-level writes (
set-realm-enabled,update-realm-settings,update-realm-smtp,update-realm-events-config,create-realm-role,delete-realm-role,create-group,delete-group) needmanage-realm.The authentication-flow and required-action tools need
view-realm(read) ormanage-realm(create/copy/delete/edit flows,set-realm-flow-binding,update-required-action).The authorization tools need
view-authorization(read,evaluate-authorization,export-authorization-settings) ormanage-authorization(create/update/delete), plusview-users/view-clientswhere a policy names users or clients.export-realmneedsview-realm(plusview-clients/view-users-level access for what it includes).partial-import-realmneeds the manage roles of the types it imports (manage-users,manage-clients,manage-realm), andimport-realmneeds the globalcreate-realmrole, so the service account must authenticate in the master realm.The organization tools need
view-realm(read) ormanage-realm(create/update/delete, members, invitations, identity-provider links), plusmanage-usersto add or remove members. They only work onceorganizationsEnabledis on for the realm.The user-federation tools need
view-realm(read) ormanage-realm(create, update, delete, sync, unlink, mappers).unlink-federated-usersandremove-imported-federated-usersalso touch users, so grantmanage-userstoo.create-realmanddelete-realmneed thecreate-realmrole (or globaladmin) in the master realm; they act across realms, so the service account must authenticate there.impersonate-userneeds theimpersonationrole.create-client/update-client/delete-client/regenerate-client-secretand the client-role tools needmanage-clients.unlock-userneedsmanage-users.list-events/list-admin-eventsneedview-events. The identity-provider tools needview-identity-providers(read) ormanage-identity-providers(create/update/delete). Protocol-mapper and client-scope tools needmanage-clients.
Install & run
npm install
npm run dev # Run the server over stdio, loading .env
npm run inspect # Launch the MCP Inspector against the server for interactive testingnpm run dev runs the TypeScript entry point directly via tsx --env-file=.env src/index.ts.
There is no separate build step.
Integrate with Claude
Claude Code (CLI)
The simplest, self-contained registration points the project's local tsx binary at the
entry file and loads secrets from .env (so no secrets appear on the command line):
# From the project root
P="$(pwd)"
claude mcp add keycloak --scope user -- \
"$P/node_modules/.bin/tsx" --env-file="$P/.env" "$P/src/index.ts"Verify it connected:
claude mcp list
# keycloak: .../tsx --env-file=.../.env .../src/index.ts - ✔ ConnectedPrefer passing env vars explicitly instead of an .env file? Use --env flags:
P="$(pwd)"
claude mcp add keycloak --scope user \
--env KEYCLOAK_BASE_URL=http://localhost:8080 \
--env KEYCLOAK_REALM=master \
--env KEYCLOAK_CLIENT_ID=keycloak-mcp \
--env KEYCLOAK_CLIENT_SECRET=your-service-account-secret \
-- "$P/node_modules/.bin/tsx" "$P/src/index.ts"To remove it later: claude mcp remove keycloak.
Claude Desktop
Edit the MCP config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add a keycloak entry under mcpServers (use absolute paths):
{
"mcpServers": {
"keycloak": {
"command": "/absolute/path/to/keycloak-mcp/node_modules/.bin/tsx",
"args": [
"--env-file=/absolute/path/to/keycloak-mcp/.env",
"/absolute/path/to/keycloak-mcp/src/index.ts"
]
}
}
}Or pass credentials inline via env instead of --env-file:
{
"mcpServers": {
"keycloak": {
"command": "/absolute/path/to/keycloak-mcp/node_modules/.bin/tsx",
"args": ["/absolute/path/to/keycloak-mcp/src/index.ts"],
"env": {
"KEYCLOAK_BASE_URL": "http://localhost:8080",
"KEYCLOAK_REALM": "master",
"KEYCLOAK_CLIENT_ID": "keycloak-mcp",
"KEYCLOAK_CLIENT_SECRET": "your-service-account-secret"
}
}
}
}Restart Claude Desktop. The Keycloak tools then appear in the tools (🔨) menu.
MCP Inspector
npm run inspectOpens the Inspector UI where you can browse and invoke each tool interactively.
Tools reference
All tools take a realm argument (the target realm) unless noted. Identifiers are
human-readable: users by username, clients by clientId, groups by path/name, roles
by name. List tools support first/max pagination (default first=0, max=50, max 200).
The tools are organised in the same groups as KEYCLOAK_TOOLS (see Tool groups),
so you can see exactly what each group exposes. A tool is only available when its group is enabled.
Users (users, 17 tools)
Tool | Description | Arguments |
| List users (id, username, email, enabled, federation link). |
|
| Get a single user by username, with profile fields and attributes. Optionally include groups and realm roles. |
|
| Count users, optionally matching a search term. Handy before paginating. |
|
| List the groups a user is a direct member of (id, name, path). |
|
| List a user's directly-assigned role mappings: realm roles plus client roles grouped by client. |
|
| List a user's credential metadata (id, type, label, created date). No secret values. |
|
| List a user's active sessions (start/last-access times, IP, clients used). |
|
| Find users by a custom attribute key/value (exact match). Paginated. |
|
| Create a user; returns the new id. Optional permanent initial password. Fails if username exists. |
|
| Update profile fields of an existing user. Only supplied fields change; needs ≥1 field. |
|
| Enable or disable an account. Disabling blocks login immediately. |
|
| Permanently delete a user. Irreversible — prefer |
|
| Set a new password. |
|
| Email the user required actions (e.g. |
|
| Revoke all of a user's active sessions, forcing re-authentication everywhere. |
|
| Start an impersonation session via the admin account. Sensitive — returns session/redirect data. |
|
| Clear a user's brute-force lockout so they can sign in again. Does not change their password. |
|
Roles (roles, 15 tools)
Composite roles bundle other roles: whoever holds the parent also gets every child. For the
composite tools the parent is a realm role, or a client role when clientId is given, and each
entry in children is { roleName, clientId? } (omit clientId for a realm role). All roles are
checked before anything is written, so a typo changes nothing.
Tool | Description | Arguments |
| List realm-level roles (id, name, description, composite flag). Search + paginate. |
|
| List roles defined by a specific client (by clientId). |
|
| List users that have a given realm role assigned. |
|
| Create a realm-level role. Fails if the name already exists. |
|
| Rename a realm role and/or change its description. Only supplied fields change; needs ≥1. |
|
| Delete a realm role by name. Irreversible — unmaps it from every user and group. |
|
| Create a role owned by a client (by clientId). Fails if the name already exists on that client. |
|
| Delete a client role by name. Irreversible — unmaps it from every user, group and composite. |
|
| Assign a realm role to a user. Idempotent. |
|
| Remove a realm role from a user. Idempotent. |
|
| Assign a client-level role to a user. Idempotent. |
|
| Remove a client-level role from a user. Idempotent. |
|
| List the child roles inside a composite role (name, description, owning |
|
| Add child roles to a role, making it composite. Idempotent for children already present. |
|
| Remove child roles from a composite role. The children themselves are kept. |
|
Groups (groups, 7 tools)
Tool | Description | Arguments |
| List groups as a tree (id, name, path, nested subGroups). Search + paginate top-level groups. |
|
| List members of a group (by path or name): id, username, email, enabled. |
|
| Create a top-level group, or a nested child when a |
|
| Rename a group (by path or name). Members, subgroups and attributes are kept; the path changes. |
|
| Delete a group (by path or name), including its subgroups. Irreversible. |
|
| Add a user to a group (by path or name). Idempotent. |
|
| Remove a user from a group (by path or name). Idempotent. |
|
Clients (clients, 8 tools)
Tool | Description | Arguments |
| List clients (id, clientId, name, enabled, protocol, public flag). Filter by clientId; paginated. |
|
| Get one client by clientId (protocol, flow settings, redirect URIs, web origins). No secret. |
|
| Retrieve a confidential client's current secret. Sensitive — non-public clients only. |
|
| Register a new client. Defaults to confidential standard-flow; toggle public / service-account. |
|
| Update an existing client. Only supplied fields change; |
|
| Delete a client, including its roles, secret and service account. Irreversible. |
|
| Rotate a confidential client's secret and return the new value. Sensitive; old secret dies. |
|
| Get the service-account user behind a client (id, username, enabled). Needs |
|
Client scopes and protocol mappers (client-scopes, 13 tools)
A client scope is a reusable bundle of protocol mappers that can be assigned to many clients.
Protocol mappers add claims to tokens, either directly on a client (add-protocol-mapper...) or on
a scope (add-client-scope-protocol-mapper...). Realm-wide default scopes (auto-assigned to new
clients) are not covered yet.
Tool | Description | Arguments |
| List the realm's client scopes, or (with |
|
| Get one scope by name: protocol, description, attributes and its protocol mappers. |
|
| Create a scope. Fails if the name already exists. |
|
| Update description and/or attributes (keys are merged). Rename/protocol change = delete + create. Needs ≥1 field. |
|
| Delete a scope and its mappers; detaches it from every client. Irreversible. |
|
| Assign a scope to a client as |
|
| Detach a scope from a client; |
|
| Add a protocol mapper to a scope. Fails if the name already exists on it. |
|
| Remove a mapper (by name) from a scope. Irreversible. |
|
| List the protocol mappers defined directly on a client (name, mapper type, config). |
|
| Add a mapper to a client, e.g. type |
|
| Change a mapper's config (looked up by name). Keys are merged; name and type can't change. |
|
| Remove a mapper (by name) from a client. Irreversible. |
|
Realms (realms, 9 tools)
Turn on event storage with update-realm-events-config before list-events /
list-admin-events (group events) return anything.
Tool | Description | Arguments |
| List realms visible to the admin service account (id, realm, enabled). Needs realm-view. | (none) |
| Get a realm's key settings: enabled, login flags, token/session lifespans, SMTP-configured. |
|
| Enable or disable a realm. Disabling blocks all logins to it immediately. |
|
| Create a new, empty realm with Keycloak defaults. Fails if the name exists. |
|
| Update login options, security ( |
|
| Read a realm's SMTP settings. The password is never returned, only |
|
| Configure outgoing email. Only supplied fields change; existing SMTP config is kept. Password is write-only. |
|
| Turn user-event and admin-event storage on/off (required before |
|
| Delete a realm and everything in it. Irreversible. |
|
Identity providers (identity-providers, 10 tools)
Identity-provider mappers turn claims from the external provider into user attributes, roles or
group memberships: call list-identity-provider-mapper-types first to get a valid mapper type and
its config keys. config on create/update may contain secrets and is never echoed back.
Tool | Description | Arguments |
| List configured identity providers (alias, provider type, display name, enabled). No secrets. |
|
| Get one provider by alias, with its settings and config. Keycloak masks secret values. |
|
| Add a social/broker provider ( |
|
| Update a provider. Only supplied fields change; |
|
| Delete a provider with its mappers and user links. Irreversible — prefer |
|
| List a provider's mappers (id, name, mapper type, config). |
|
| List the mapper types a provider supports, with their config properties. |
|
| Add a mapper, e.g. |
|
| Change a mapper's config (looked up by name). Keys are merged; name and type can't change. |
|
| Remove a mapper (by name). Already-imported users keep what it set. Irreversible. |
|
Authentication flows and required actions (authentication, 13 tools)
Flows decide how users log in (password, OTP, social login...). Flows are addressed by alias,
and steps ("executions") by id, or by provider id / display name when that is unambiguous.
Built-in flows can't be edited: copy-authentication-flow first, edit the copy, then bind it with
set-realm-flow-binding. Authenticator configs (e.g. OTP policy options on a step) and an identity
provider's first-broker-login flow (set on the identity provider) are not covered yet.
Tool | Description | Arguments |
| List top-level flows (alias, description, built-in) and which realm bindings use each ( |
|
| Show a flow's steps in order with nesting level, requirement, provider and allowed requirement values. |
|
| List step types you can add ( |
|
| Create an empty top-level flow. Does nothing until it has steps and is bound. |
|
| Copy a flow (usually a built-in) under a new alias, with its subflows and steps. |
|
| Delete a custom flow. Built-in and realm-bound flows are refused. Irreversible. |
|
| Add a step to a flow/subflow. New steps start |
|
| Add a nested subflow ( |
|
| Set a step's requirement: |
|
| Remove a step. Deleting a subflow step deletes everything inside it. Irreversible. |
|
| Choose the flow used for |
|
| List required actions ( |
|
| Enable/disable an action, rename it, or make it a default action assigned to every new user. Needs ≥1 field. |
|
Authorization services (authorization, 17 tools)
Authorization services add fine-grained access control to a client (the resource server). All
tools take the resource server's clientId, and everything is referenced by name. The model:
resources (what is protected) carry scopes (actions such as view/edit); policies say who or when
(role, user, group, time...); a permission ties resources/scopes to the policies that must be
satisfied. Build them in that order, then check the outcome with evaluate-authorization. Enable the
feature first with update-client (authorizationServicesEnabled=true, confidential clients only).
Editing an existing policy or permission, and importing a full settings JSON, are not covered: delete
and re-create. export-authorization-settings shows the full picture, including policy members.
Tool | Description | Arguments |
| Get a resource server's settings: enforcement mode, decision strategy, remote resource management. |
|
| Change enforcement mode ( |
|
| Export the full authorization config (settings, scopes, resources, policies, permissions) as JSON, members by name. Can be large. |
|
| Dry-run: would a user be permitted to access a resource/scopes, and which policies decided it? Changes nothing. |
|
| List the resource server's authorization scopes (actions such as |
|
| Create an authorization scope. Fails if the name exists. |
|
| Delete a scope; it is removed from every resource and scope permission using it. Irreversible. |
|
| List protected resources with type, URIs and attached scopes. Filterable; paginated. |
|
| Create a protected resource. Scopes are given by name and must already exist. Fails if the name exists. |
|
| Update a resource by name. |
|
| Delete a protected resource. Irreversible. |
|
| List policies (name, type, logic, decision strategy). Use |
|
| Create a policy of type |
|
| Delete a policy; permissions that used it lose it, which can silently widen or narrow access. Irreversible. |
|
| List permissions (name, type, decision strategy); |
|
| Grant access: tie resources (or a |
|
| Delete a permission; the resources and policies it linked are kept. Irreversible. |
|
Organizations (organizations, 15 tools)
Organizations group users into customers/tenants (Keycloak 26+), each with its own email domains and
optionally its own identity providers. Turn the feature on first with update-realm-settings
(organizationsEnabled=true). Organizations are addressed by name or alias, members by
username, invitations by the invited email. Organization groups and per-organization
identity-provider domain settings are not covered yet.
Tool | Description | Arguments |
| List organizations (name, alias, enabled, email domains). |
|
| Get one organization by name or alias: description, redirect URL, domains, attributes and linked identity providers. |
|
| Create an organization. |
|
| Update an organization. Only supplied fields change; |
|
| Delete an organization with its memberships, invitations and IdP links. Users it manages may be deleted too. Irreversible. |
|
| List members with their membership type ( |
|
| Add an existing user (by username) as an unmanaged member. Fails if already a member. |
|
| Remove a member. A managed member may be deleted with the membership. |
|
| List the organizations a user belongs to. |
|
| Email an invitation. Existing users (matched by email) are invited as existing users; others can register. Needs SMTP. |
|
| List invitations: email, name, status ( |
|
| Send an invitation again (identified by email). Needs SMTP. |
|
| Cancel an invitation (identified by email). Irreversible. |
|
| Link an existing identity provider to an organization. A provider can belong to only one organization. |
|
| Detach an identity provider from an organization; the provider itself is kept. |
|
Realm import and export (import-export, 3 tools)
Back up a realm or copy its setup to another. export-realm writes realm configuration as JSON;
partial-import-realm loads resources into an existing realm and import-realm creates a new one.
A file is given as an absolute path ending in .json; set KEYCLOAK_FILES_DIR to confine every
read and write to one directory (see Environment variables). Exports do
not contain users, and Keycloak masks secrets (**********) in them, so after an import the
secrets of clients, identity providers, SMTP and LDAP must be set again. Large exports should go to
a file rather than into the conversation.
Tool | Description | Arguments |
| Export a realm as JSON: settings, flows, identity providers and optionally clients, groups and roles. Users are not included; secrets come back masked. |
|
| Import users, clients, groups, roles and identity providers from a realm JSON into an existing realm. |
|
| Create a new realm from a full realm JSON. |
|
User federation (LDAP / Active Directory) (federation, 12 tools)
Federation providers let Keycloak authenticate users against an external directory. Providers and
their mappers are addressed by name. Secrets (the bind credential) are write-only: they are
never returned, and get-user-federation-provider only lists which ones are set.
Kerberos and custom federation providers can be listed, inspected, updated, synced and deleted, but only LDAP/AD providers can be created. Editing an existing mapper and triggering a mapper sync (group/role import) are not covered; delete and re-create a mapper to change it.
Tool | Description | Arguments |
| List providers: name, type, enabled, priority, edit mode and (LDAP) connection URL. |
|
| Get one provider with its full config. Secrets omitted ( |
|
| Connect an LDAP/AD server. |
|
| Change settings; |
|
| Delete a provider and its mappers. Keycloak also removes the users imported from it. Irreversible. |
|
| Import users now: |
|
| Turn all of a provider's users into ordinary local users (they then need a local password). Run before deleting a provider to keep its users. |
|
| Delete Keycloak's copies of all users imported from a provider. They are re-imported on next login/sync. Irreversible for Keycloak-only data. |
|
| List the mapper types a provider supports, with their config properties. |
|
| List a provider's mappers (name, type, config). |
|
| Add a mapper ( |
|
| Remove a mapper by name. Irreversible. |
|
Events (events, 2 tools)
Both tools need event storage enabled (update-realm-events-config, group realms); otherwise
they return an empty list.
Tool | Description | Arguments |
| List login/user events (LOGIN, LOGIN_ERROR, LOGOUT, ...), newest first. Handy for failed-login debugging. |
|
| List admin-API events (who created/updated/deleted what), newest first. |
|
Usage tips
Once integrated, you can prompt Claude in natural language, for example:
“List the first 10 users in the
financement-realmrealm whose name containsdupont.”“Show details for user
jdoeinfinancement-realm, including their groups and realm roles.”“Disable the account
olduserinfinancement-realm.”“Assign the
offline_accessrealm role tojdoeinfinancement-realm.”“Set
jdoe's email tojdoe@example.comand mark it verified.”“Send
jdoea VERIFY_EMAIL and UPDATE_PASSWORD action email.”“Log
jdoeout of all sessions infinancement-realm.”“Create a
billing-adminrealm role and assign it tojdoe.”“Rotate the client secret for
my-backendinfinancement-realm.”“Find all users in
financement-realmwith attributedepartment = finance.”“Why did
jdoe's login fail yesterday infinancement-realm?” (login events)“Add a
departmentclaim mapper to themy-backendclient.”“Make
billing-admina composite role that includesoffline_access.”“Copy the
browserflow tobrowser-with-otp, make OTP required, then bind it to the realm.”“Why can't
jdoeview theinvoicesresource ofmy-backend?” (authorization evaluation)“Let the
financegroup view and editinvoicesinmy-backend.”“Export
financement-realmto/Users/me/backups/financement.json.”“Clone
financement-realmasstaging-realmfrom that file.”“Create an organization
Acmewith the domainacme.com, then inviteanna@acme.comto it.”“Connect
financement-realmto our Active Directory atldaps://ad.example.comand sync the users.”
Claude will pick the matching tool and fill in the arguments.
⚠️ Destructive tools have no confirmation step. Every
delete-*tool,remove-imported-federated-users,unlink-federated-users,logout-user,regenerate-client-secret,set-realm-enabled(false),set-realm-flow-bindingandpartial-import-realmwithOVERWRITEtake effect immediately, and most cannot be undone.delete-realmis the one exception: it needs aconfirmargument repeating the realm name and refuses themasterrealm. A badset-realm-flow-bindingcan lock everyone out of a realm; inspect the flow first withget-authentication-flow. To limit what the model can do, enable fewer groups withKEYCLOAK_TOOLSand grant the service account only the roles it needs.
Troubleshooting
Symptom | Likely cause / fix |
Server won't connect in | Check absolute paths; run |
| Wrong |
Tool returns "not found" | Verify |
| Client is public (no secret) — only confidential clients have one. |
| The target realm has no SMTP server configured. |
| Service account lacks |
| Needs |
Missing users/clients in list | Service account lacks |
Server exits at startup with | A name in |
A tool is missing from the client | Its group is not enabled. Check the startup line on stderr ( |
| Event storage is off for that realm. Enable it with |
| Enable them with |
| They are referenced by name and must exist first. Create in order: scopes, resources, policies, then the permission. |
Import/export says | Paths must be absolute, end in |
Imported clients/identity providers can't authenticate | Exports mask secrets and the import drops them. Regenerate client secrets ( |
| Turn the feature on with |
| The realm has no SMTP server configured; see |
LDAP sync reports | Check |
Changes not visible in Claude Desktop | Fully restart the app after editing the config. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Every Canopy public API operation as a tool, run as you after a browser sign-in or on an API key.
Access Pollinations models and API capabilities through agent tools.
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- 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.987 npm13MIT
- AlicenseCqualityDmaintenanceEnables 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.1003MIT
- 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
- AlicenseCqualityDmaintenanceA 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.86MIT