MCP server implementation for Keycloak user management. Enables AI-powered administration of Keycloak users and realm...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Universal
Model
Multiple
Fastest way to find out if keycloak-model-context-protocol belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add keycloak-model-context-protocol -- npx keycloak-model-context-protocolRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove keycloak-model-context-protocolNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ keycloak-model-context-protocol ← registers here
MCP server implementation for Keycloak user management. Enables AI-powered administration of Keycloak users and realms through the Model Context Protocol (MCP). Seamlessly integrates with Claude Desktop and other MCP clients for automated user operations.
Source: GitHub repository
Source check: October 24, 2026
Upstream commit: October 24, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.