Sponsored Demo: MCP Auth Demo: CIMD With Keycloak
summary
Keycloak implements the MCP authorization model (spec v2025-11-25) by retrieving and validating Client ID Metadata Documents (CIMD) hosted at an HTTPS URL, then issuing OAuth access tokens used by MCP clients. The demo uses MCP Inspector as client, a Python SDK MCP server with a Hello tool, and a CIMD on hitachi.github.io; Keycloak fetches the CIMD, validates ownership, performs user auth and consent, dynamically registers the client, issues a token, and the Hello tool runs successfully. CIMD replaces DCR as the recommended dynamic method.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:42Model Context Protocol
- 2:33MCP authorization
- 5:00Client registration
- 7:51CIMD authorization
- 11:04Demo setup
- 12:12CIMD flow with Keycloak
- 16:30Summary
related talks
27mSimple Control: Managing Multi-Domain MCP Access Via Keycloak IdP With ID-JAG
32mAI Agents with Keycloak in MCP
11mLightning Talk: Effortlessly Integrating Keycloak Authentication To Your MCP Servers
25mModel Context Protocol(MCP) Authorization for Enterprise Use Case With Keycloak
17mMCP auth: Stop registering, Start linking
25mSecure Your MCP Servers With OAuth, JWT, SPIFFE and More
26mSecure Your MCP Servers with OAuth, JWT, SPIFFE and More
27mMCPIdentity: Keyless MCP Agent Authentication Patterns on Kubernetes With Keycloak…