Keycloak MCP Server

Created By
ChristophEnglischa year ago
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.
Overview

What is Keycloak MCP Server?

Keycloak MCP Server is an implementation of the Model Context Protocol (MCP) for managing Keycloak users and realms, enabling AI-powered administration.

How to use Keycloak MCP Server?

To use the Keycloak MCP Server, install it via NPM or Smithery, configure it with your Keycloak instance, and utilize the provided tools for user management.

Key features of Keycloak MCP Server?

  • Create and delete users in specific realms
  • List available realms and users in those realms
  • Seamless integration with Claude Desktop and other MCP clients

Use cases of Keycloak MCP Server?

  1. Automating user management tasks in Keycloak
  2. Integrating AI tools for enhanced user administration
  3. Managing multiple realms efficiently

FAQ from Keycloak MCP Server?

  • Can I use Keycloak MCP Server with any Keycloak version?

Yes, as long as the Keycloak instance is compatible with the Model Context Protocol.

  • Is there a graphical interface for managing users?

The server is primarily command-line based, but it integrates with tools like Claude Desktop for a more user-friendly experience.

  • How do I report issues or contribute to the project?

You can report issues or contribute by visiting the project's GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ChristophEnglisch
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago