How do I authenticate with the server?
Users authenticate by obtaining a JWT token from their Keycloak instance (using the provided `get-mcp-token.sh` script) and passing it as a Bearer token in the Authorization header of SSE requests.
@sshaaf
Basic information
An MCP server for Keycloak, designed to work with Keycloak for identity and access management, covering, Users, Realms, Clients, Roles, Groups, IDPs, Authentication. Searching keycloak discourse, Native builds available.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"keycloak-mcp-server": {
"command": "docker",
"args": [
"run",
"-d",
"\\"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Keycloak MCP Server is a Model Context Protocol (MCP) server that provides programmatic access to Keycloak administration functionality. It enables AI assistants and development tools to interact with Keycloak through the MCP protocol.
Run the server via Docker with environment variables for Keycloak URL, realm, and OIDC client ID. Users authenticate with their own JWT tokens obtained from Keycloak, then configure their MCP client (e.g., in ~/.cursor/mcp.json) with SSE transport and an Authorization header containing the token.
Users authenticate by obtaining a JWT token from their Keycloak instance (using the provided `get-mcp-token.sh` script) and passing it as a Bearer token in the Authorization header of SSE requests.
The server is built on Quarkus and can run as a JAR, native image, or container. Docker is the recommended deployment method, with pre-built images available on Quay.io.
Keycloak MCP Server does not store data itself—it communicates with an external Keycloak server whose URL is provided via the `KC_URL` environment variable. All user, realm, and client data resides in that Keycloak instance.
The server uses SSE (Server-Sent Events) transport for MCP communication. Authentication is handled via user-specific JWT tokens issued by Keycloak.
No limitations or alternative servers are discussed in the README. The server focuses on providing comprehensive Keycloak administration via MCP.

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews — all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1–3
Hindsight: Agent Memory That Learns

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code
YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
Comments