skycloak-mcp
Related Servers
Alternatives to skycloak-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides a natural language interface for managing Keycloak identity and access management through its REST API.MIT
- AlicenseCqualityDmaintenanceA comprehensive MCP server for Keycloak administration, offering 80+ tools to manage users, realms, clients, roles, groups, sessions, events, organizations, and more directly from AI assistants.86MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an AI assistant inspect and modify Keycloak realm, client, and protocol-mapper configuration across multiple Keycloak hosts.7MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for managing Ory Kratos identities, sessions, and authentication flows, enabling AI assistants to perform identity management tasks via natural language.13 npm1MIT

keyshade-mcpofficial
AlicenseBqualityDmaintenanceMCP server for interacting with Keyshade's secrets management platform, enabling secure retrieval and management of secrets via natural language.449Mozilla Public 2.0- AlicenseNot gradedqualityBmaintenanceMCP server for Authentik identity management, enabling natural language management of users, groups, applications, flows, policies, providers, and more.468 npm17MIT
TDQS
Scored across 141 tools
Despite 141 tools, nearly every one names a distinct resource+operation, and descriptions actively disambiguate neighbours (e.g. list_realm_roles vs list_user_roles vs list_application_roles, get_logs vs get_security_logs vs query_events, update_theme vs update_theme_content vs update_theme_settings). The dense theme/branding cluster and the three role surfaces still require careful reading, so it is not a clean 5, but misselection should be rare.
All tools use a uniform skycloak_ prefix plus snake_case verb_noun (list_, get_, create_, update_, delete_, test_, set_, remove_), consistently suffixed by the resource. Minor verb variance exists for grant/revoke semantics (add_ vs assign_ vs create_, remove_ vs delete_) and for upsert_ vs create_/update_ on branding and SMTP, but the pattern stays readable throughout.
141 tools is far beyond what an agent can navigate reliably in one surface, even though the domain (clusters, realms, users, roles, groups, SSO, themes, branding, SMTP, webhooks, SIEM, extensions, OpenFGA, exports, logging) genuinely justifies substantial breadth. The set would benefit from consolidation (e.g. theme settings/assignment split across six tools, near-duplicate get_ variants) rather than one tool per endpoint.
Coverage is unusually thorough: most resources have full list/get/create/update/delete plus async polling counterparts, and cross-references close loops between related tools. Gaps remain around session control (list_application_sessions cannot revoke), realm export listing, user password management, and client scopes/keys, but these are workaround-able rather than blocking.