by christophenglisch
Keycloak Admin plugin enables seamless user and realm management for automated identity and access control solutions.
Provides admin tools to manage Keycloak identity server, allowing you to create/delete users and manage realms through a simple interface.
Keycloak Admin is a community-built MCP server published by christophenglisch that provides AI assistants with tools and capabilities via the Model Context Protocol. Keycloak Admin plugin enables seamless user and realm management for automated identity and access control solutions. It is categorized under productivity, developer tools.
You can install Keycloak Admin 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 Admin 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 Admin is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Keycloak Admin against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, Keycloak Admin benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Keycloak Admin reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Keycloak Admin has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: Keycloak Admin is the kind of server we cite when onboarding engineers to host + tool permissions.
Keycloak Admin is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Keycloak Admin reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Keycloak Admin for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Keycloak Admin surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 56
A Model Context Protocol server for Keycloak administration, providing tools to manage users and realms.
To install Keycloak for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install keycloak-model-context-protocol --client claude
The server is available as an NPM package:
# Direct usage with npx
npx -y keycloak-model-context-protocol
# Or global installation
npm install -g keycloak-model-context-protocol
If you want to develop or modify the server:
git clone <repository-url>
cd keycloak-model-context-protocol
npm install
npm run build
Configure the server in your Claude Desktop configuration file:
{
"mcpServers": {
"keycloak": {
"command": "npx",
"args": ["-y", "keycloak-model-context-protocol"],
"env": {
"KEYCLOAK_URL": "http://localhost:8080",
"KEYCLOAK_ADMIN": "admin",
"KEYCLOAK_ADMIN_PASSWORD": "admin"
}
}
}
}
{
"mcpServers": {
"keycloak": {
"command": "node",
"args": ["path/to/dist/index.js"],
"env": {
"KEYCLOAK_URL": "http://localhost:8080",
"KEYCLOAK_ADMIN": "admin",
"KEYCLOAK_ADMIN_PASSWORD": "admin"
}
}
}
}
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 namenpm run watch
To test the server using MCP Inspector:
npx -y @modelcontextprotocol/inspector npx -y keycloak-model-context-protocol
This project is automatically published to NPM via GitHub Actions when a new release is published on GitHub.
NPM_TOKENPrerequisites
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.