Server facts
keycloak-mcp
Project
- Author
- Octodet
- Repository
- github.com/Octodet/keycloak-mcp
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- identity
- keycloak
- roles
- users
Overview
Realm discovery and account maintenance form the core of keycloak-mcp's administrative workflow. Administrators can inspect available realms, then retrieve usernames and user IDs within a selected realm. Account creation accepts a username, email address, and first and last names, with optional settings for account enablement, email verification, and credentials. Credential settings can mark a password as temporary so it must be changed at first login. Creation returns the new account's ID and a confirmation. Separate tools delete an account permanently or reset or set its password.
Client access is handled through role inspection and assignment changes. A client can be selected using its readable ID or UUID, and its role names can be listed before modifying a user's assignments. The role-update tool accepts additions, removals, or both together, and reports changes alongside any errors. Unknown role names are skipped with warnings. These tools expose realm, account, and client-role administration over MCP using the stdio transport.
keycloak-mcp setup notes
- keycloak-mcp records stdio only; confirm a network transport upstream before planning remote access.
- keycloak-mcp has no recorded license; confirm reuse terms in its repository.