How to Use the Keycloak MCP in Windsurf

Q: How do I connect the Keycloak MCP Server to Windsurf?

Open /.codeium/windsurf/mcpconfig.json and add the Keycloak server details under the mcpServers object. You can also use the Settings → Cascade → MCP Servers UI to configure it visually. Hit refresh, and Cascade immediately discovers all 34 IAM tools.

Q: Does Cascade support custom authentication flows?

It does. The server includes createauthflow and listauthflows. You can instruct your agent to mirror a complex production login sequence right in your local testing environment.

Q: How does this MCP server handle user data privacy?

When your agent calls getuser or listusers, it retrieves raw PII including email addresses, usernames, and group memberships. Vinkius isolates this execution inside an ephemeral V8 sandbox, meaning the token and the resulting identity payload exist only for the duration of the query and never touch persistent storage.

Manage Keycloak identity realms, clients, and users directly through Windsurf using autonomous multi-tool execution.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Keycloak MCP to Windsurf

Create your Vinkius account to connect Keycloak to Windsurf and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Keycloak with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Cascade-Driven Keycloak MCP Server

The Keycloak MCP Server exposes 34 identity management tools directly to Cascade. You tell Windsurf to stand up a new B2B tenant, and it fires off `create_realm`, configures the OIDC endpoints with `create_client`, and provisions the initial admin via `create_user` without stopping to ask for permission. That autonomy changes how you handle IAM tasks during development. Instead of clicking through the Keycloak admin console to map roles, Cascade reads your project requirements, executes `create_role`, and binds it to your test accounts using `update_user` in one continuous motion.

Instant Identity State Validation

Checking access control configurations usually means digging through logs or API responses. Windsurf fixes that by running `list_user_groups` or `get_role` mid-session and dropping the exact JSON representation right into your editor context. If a login flow breaks while you code, Cascade can immediately pull `list_admin_events` to trace the failure. It spots the missing client secret, calls `regenerate_client_secret`, and patches your local `.env` file before you even switch windows.

Bulk Tenant Operations

Managing multiple environments gets messy fast. Windsurf handles the heavy lifting by chaining `partial_export_realm` from your staging setup and pushing the structure to local dev using `import_realm`. When you finish testing a destructive feature, you don't leave orphaned data behind. Cascade can clean up the entire test environment by executing `logout_all_users` followed by `delete_realm`, keeping your local Keycloak instance perfectly clean.

Setup guide

Set up Keycloak MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the Keycloak MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Keycloak payment history." If connected, Cascade will call the Keycloak tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "keycloak-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Keycloak. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Keycloak now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Keycloak MCP in Windsurf

Open `~/.codeium/windsurf/mcp_config.json` and add the Keycloak server details under the `mcpServers` object. You can also use the Settings → Cascade → MCP Servers UI to configure it visually. Hit refresh, and Cascade immediately discovers all 34 IAM tools.

Yes. Cascade excels at multi-step executions. If you ask it to build a new permission tier, it will run `create_group`, then `create_role`, and finally bind them together without waiting for your approval between steps.

You likely need to check your admin token permissions. Destructive tools like `delete_realm` or `delete_client` require strict authorization at the Keycloak level, even if the MCP connection itself is active.

It does. The server includes `create_auth_flow` and `list_auth_flows`. You can instruct your agent to mirror a complex production login sequence right in your local testing environment.

When your agent calls `get_user` or `list_users`, it retrieves raw PII including email addresses, usernames, and group memberships. Vinkius isolates this execution inside an ephemeral V8 sandbox, meaning the token and the resulting identity payload exist only for the duration of the query and never touch persistent storage.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript