4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Keycloak MCP Server

Bring Iam
to CrewAI

Learn how to connect Keycloak to CrewAI and start using 34 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create Auth FlowCreate ClientCreate GroupCreate RoleCreate UserDelete ClientDelete GroupDelete RealmDelete UserGet ClientGet Client SecretGet GroupGet RealmGet RoleGet UserImport RealmList Admin EventsList Auth FlowsList Client RolesList ClientsList GroupsList RealmsList Required ActionsList RolesList User GroupsList UsersLogout All UsersPartial Export RealmRegenerate Client SecretReset User PasswordUpdate ClientUpdate GroupUpdate RealmUpdate User

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Keycloak

What is the Keycloak MCP Server?

Connect your Keycloak instance to any AI agent to streamline your Identity and Access Management (IAM) workflows. This server provides comprehensive tools to audit, configure, and maintain your security infrastructure through natural language.

What you can do

  • Realm Administration — List, import, and export realms, or monitor admin events to audit changes across your infrastructure.
  • User Management — Create, update, or delete users, reset passwords, and inspect user group memberships without leaving your chat interface.
  • Client Configuration — Manage OIDC/SAML clients, retrieve client secrets, and regenerate credentials instantly.
  • Groups & Roles — Organize your security hierarchy by managing groups and assigning roles at both realm and client levels.
  • Session Control — Force global logouts across entire realms to mitigate security threats in real-time.

How it works

  1. Subscribe to this server
  2. Provide your Keycloak Base URL and a valid Admin Access Token
  3. Start managing your IAM infrastructure from Claude, Cursor, or any MCP client

Who is this for?

  • DevOps & SREs — Quickly audit realm events and manage client configurations during deployments.
  • Security Administrators — Perform emergency password resets or session terminations via simple commands.
  • Backend Developers — Setup test users and retrieve client credentials directly within the IDE flow.

Built-in capabilities (34)

create_auth_flow

Create an authentication flow

create_client

Create a new client

create_group

Create a top-level group

create_role

Create a realm-level role

create_user

Create a new user

delete_client

Delete a client

delete_group

Delete a group

delete_realm

Delete a realm

delete_user

Delete a user

get_client

Get client representation

get_client_secret

Get client secret

get_group

Get group representation

get_realm

Get realm representation

get_role

Get a role by name

get_user

Get user representation

import_realm

Import a realm

list_admin_events

Get admin events for a realm

list_auth_flows

Get authentication flows

list_client_roles

Get client-level roles

list_clients

Get all clients in the realm

list_groups

Get group hierarchy

list_realms

Get accessible realms

list_required_actions

Get required actions

list_roles

Get realm-level roles

list_user_groups

Get user groups

list_users

Get users in a realm

logout_all_users

Remove all user sessions in a realm

partial_export_realm

Partial export of a realm

regenerate_client_secret

Regenerate client secret

reset_user_password

Reset user password

update_client

Update a client

update_group

Update a group

update_realm

Update realm information

update_user

Update a user

Why CrewAI?

When paired with CrewAI, Keycloak becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Keycloak tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Keycloak in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Keycloak and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Keycloak to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Keycloak in CrewAI

The Keycloak MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 34 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Keycloak
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Keycloak for CrewAI

Every tool call from CrewAI to the Keycloak MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I reset a user's password using this integration?

Yes. You can use the reset_user_password tool by providing the realm name, the user ID, and the new credential representation. This allows for immediate password management via the AI.

02

Is it possible to audit administrative changes in a specific realm?

Absolutely. The list_admin_events tool retrieves the history of administrative actions for a target realm, helping you track who changed what and when.

03

Can I retrieve OIDC client secrets for my applications?

Yes, the get_client_secret tool allows you to fetch the secret for any configured client in a realm. You can also use regenerate_client_secret if a rotation is required.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →