MCP server
by haithamoumerzoug
Integrate with Keycloak for user creation, role assignment, group, and client management across realms using Keycloak id
Connects to Keycloak identity management systems to manage users, realms, groups, and clients through a standardized interface.
Keycloak is a community-built MCP server published by haithamoumerzoug that provides AI assistants with tools and capabilities via the Model Context Protocol. Integrate with Keycloak for user creation, role assignment, group, and client management across realms using Keycloak id It is categorized under auth security.
You can install Keycloak in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Keycloak is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Keycloak is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Keycloak surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Keycloak reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Keycloak for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Keycloak into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: Keycloak surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Useful MCP listing: Keycloak is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Keycloak surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Keycloak is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Keycloak for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 48
A Model Context Protocol (MCP) server implementation for Keycloak, providing a standardized interface for managing Keycloak users and realms.
<a href="https://glama.ai/mcp/servers/@HaithamOumerzoug/keycloak-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@HaithamOumerzoug/keycloak-mcp/badge" alt="Keycloak Server MCP server" /> </a>This project implements an MCP server that integrates with Keycloak, allowing you to manage Keycloak users and realms through a standardized protocol. It uses the official Keycloak Admin Client to interact with Keycloak's API.
https://github.com/user-attachments/assets/4b02a049-b8d6-4cc5-a7b4-564a0e758dd8
Creates a new user in a specified realm.
Inputs:
realm: The realm nameusername: Username for the new useremail: Email address for the userfirstName: User's first namelastName: User's last nameDeletes a user from a specified realm.
Inputs:
realm: The realm nameuserId: The ID of the user to deleteLists all available realms.
Lists all users in a specified realm.
Inputs:
realm: The realm nameLists all clients in a specified realm.
Inputs:
realm: The realm nameLists all groups in a specified realm.
Inputs:
realm: The realm nameLists all roles for a specific client in a realm.
Inputs:
realm: The realm nameclientUniqueId: The unique ID of the clientAssigns a client role to a specific user.
Inputs:
realm: The realm nameuserId: The ID of the userclientUniqueId: The unique ID of the clientroleName: The name of the role to assignAdds a user to a specific group.
Inputs:
realm: The realm nameuserId: The ID of the usergroupId: The ID of the groupTo install keycloak-mcp for Claude Desktop automatically via Smithery:
$ npx -y @smithery/cli install @HaithamOumerzoug/keycloak-mcp --client claude
--keycloak-url <Keycloak Instance URL>--keycloak-admin <Admin Username>--keycloak-admin-password <Admin Password>The server is available as an NPM package:
# Direct usage with npx
$ npx -y keycloak-mcp --keycloak-url <Keycloak Instance URL> --keycloak-admin <Admin Username> --keycloak-admin-password <Admin Password>
# Or global installation
$ npm install -g keycloak-mcp@latest
$ keycloak-mcp --keycloak-url <Keycloak Instance URL> --keycloak-admin <Admin Username> --keycloak-admin-password <Admin Password>
Configure the server in your Cursor IDE, Cline or Claude Desktop MCP configuration file:
{
"mcpServers": {
"keycloak": {
"command": "npx",
"args": ["-y", "keycloak-mcp"],
"env": {
"KEYCLOAK_URL": "http://localhost:8080",
"KEYCLOAK_ADMIN": "admin",
"KEYCLOAK_ADMIN_PASSWORD": "admin"
}
}
}
}
{
"mcpServers": {
"keycloak": {
"command": "node",
"args": ["path/to/dist/server.js"],
"env": {
"KEYCLOAK_URL": "http://localhost:8080",
"KEYCLOAK_ADMIN": "admin",
"KEYCLOAK_ADMIN_PASSWORD": "admin"
}
}
}
}
To set up the development environment:
npm install
cp .env.template .env
# Edit the .env file and set all variables with the appropriate values
npm run dev
npm run build - Builds the project and makes the CLI executablenpm run prepare - Runs the build script (used during package installation)npm run dev - Watches for changes and rebuilds automaticallynpm start - Starts the server (for production)@keycloak/keycloak-admin-client - Official Keycloak Admin Client@modelcontextprotocol/sdk - MCP SDK for standardized protocol implementationzod - TypeScript-first schema validationchalk - Terminal string stylingyargs - Parsing command-line argumentstypescript - For TypeScript support@types/node - TypeScript definitions for Node.jsshx - Cross-platform shell commandsts-node - TypeScript execution and REPL for Node.jsrimraf - A cross-platform tool to remove directories@types/yargs - TypeScript definitions for yargsMIT
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.