Keycloak is an open source identity and access management solution that provides single sign-on, identity federation, and user management capabilities for modern applications and services.
Supports OAuth 2.1 authentication integration with Keycloak for enterprise-grade security with granular access control scopes and RFC-compliant identity provider integration.
Comprehensive Model Context Protocol server for MySQL databases featuring 191 specialized tools for CRUD operations, JSON functions, spatial/GIS, schema management, performance monitoring, and advanced features like OAuth 2.1 authentication and connection pooling.
43
52 npm
11
MIT
Why this server?
Integrate with Keycloak for OIDC authentication to secure HTTP deployments of the MCP server.
A generic Markdown vault MCP server with FTS5 full-text search, semantic vector search, frontmatter-aware indexing, incremental reindexing, and non-markdown attachment support that exposes search, read, write, and edit tools.
44
699 PyPI
34
MIT
Why this server?
Provides OIDC/OAuth 2.0 identity layer with RBAC, service accounts, and authentication capabilities similar to Keycloak but integrated with API credential injection.
Agent Connectivity Gateway — turn any authenticated API into an MCP Server. Self-hosted reverse proxy with OAuth 2.0/OIDC credential injection, per-agent isolation,
NAT traversal for localhost services, and REST-to-MCP auto-wrap from OpenAPI specs. Works with Claude Code, Cursor, Codex. Rust.
4
38
Apache 2.0
Why this server?
Integration with Keycloak as an OpenID Connect provider for authentication to the LaSuite Docs API.
MCP server for LaSuite Docs API, enabling operations like list, read, create, update, delete documents, versions, favorites, and current user via OIDC authentication.
14
MIT
Why this server?
Supports OIDC/JWT authentication via Keycloak or any OpenID Connect provider for secure enterprise authentication to SAP systems.
Supports OIDC-based authentication with Keycloak as an identity provider, including JWT/JWKS validation, issuer/audience checks, and custom roles claims such as Keycloak's realm_access.roles style paths.
Provides a security governance layer for AI agents to safely access upstream MCP servers, enforcing tool-level RBAC, parameter constraints, authentication via static tokens or OIDC, and tamper-evident audit logging.
2
1
Apache 2.0
Why this server?
Provides tools for Keycloak administration, allowing management of users and realms including creating and deleting users, listing available realms, and viewing users within specific realms.
A Model Context Protocol server that provides tools to manage Keycloak users and realms, allowing you to create and delete users, list available realms, and view users in specific realms.
4
41 npm
46
MIT
Why this server?
Provides tools for managing Keycloak users, groups, security, events, sessions, and clients through the Keycloak Admin REST API via service account authentication.
An MCP server for Keycloak Admin REST API, enabling user, group, event, and security management through service account authentication.
32
218 PyPI
MIT
Why this server?
Provides tools to explore and administer a Keycloak instance, covering realms, users, groups, roles, clients, sessions, events, client scopes, protocol mappers, identity providers, and authentication flows. Read-only by default, with optional write operations.
Enables AI agents to explore and administer a Keycloak instance via the Keycloak Admin REST API, covering realms, users, groups, roles, clients, sessions, events, client scopes, identity providers, and authentication flows, with read-only operation by default and optional write tools.