Presenters

Source

Seamlessly Integrate Keycloak Authentication with Your MCP Server 🚀

Ever wished you could secure your MCP servers without diving deep into code modifications and complex redeployments? Well, buckle up, because Lin Song from Solo.io is here to show us how! In this insightful session from Keycloak Kong, Lin walks us through integrating Keycloak authentication into an MCP server, demonstrating a powerful approach using a gateway.

The Humble Echo Server: Our Starting Point 🗣️

Lin kicks things off by introducing a straightforward MCP server built with Python. This server, running on localhost:8000, acts as a simple echo service. It’s annotated with mcp.tools and features a basic echo tool that returns messages and their repetition count.

To verify its functionality, Lin uses the MCP Inspector. Think of the MCP Inspector as your friendly MCP client, perfect for testing and interacting with MCP servers. By connecting to the running echo server and invoking the echo tool, Lin confirms that the server is indeed operational.

  • Key Takeaway: A basic MCP server can be easily set up and tested with tools like the MCP Inspector.

The Challenge: Adding Authentication Without the Hassle 🛡️

While the echo server works perfectly, it lacks any form of authentication. The traditional approach would involve modifying the MCP server’s code, specifying Keycloak as a remote authentication provider using OpenID Connect, and then rebuilding and redeploying the entire application. This process can be tedious and time-consuming, especially for simple services.

Lin highlights the drawbacks of this method:

  • Code Modification: Requires changes to the core application logic.
  • Rebuild & Redeploy: Involves a significant overhead for even minor configuration changes.

The Elegant Solution: Leveraging an MCP Gateway 🌐

Here’s where the magic happens! Lin introduces Agent Gateway as a game-changer. Instead of altering the MCP server code, Agent Gateway acts as a proxy, allowing you to configure authentication and authorization externally. This means your original MCP server remains untouched, making it incredibly flexible and maintainable.

Configuring Authentication with Agent Gateway 🔑

Lin demonstrates how to configure Agent Gateway with Keycloak authentication. This involves setting up:

  • Issuer: The Keycloak realm URL.
  • Audience: The identifier for your MCP server.
  • Token Validation: Agent Gateway validates tokens issued by Keycloak, ensuring only authorized requests reach your MCP server.

This configuration is applied to the Agent Gateway, which then forwards requests to the original MCP server running on port 8000. The Agent Gateway itself is configured to listen on port 9000.

  • Key Benefit: No modification needed for the original MCP server code.
  • Flexibility: Authentication and authorization are managed externally via the gateway.

The Live Demo (and a Touch of Real-World Debugging!) 😅

Lin then proceeds to a live demonstration, showcasing the Agent Gateway in action. The goal is to connect to the MCP Inspector, but this time pointing to the Agent Gateway on port 9000.

Initially, the demo encounters a hiccup: the MCP Inspector connects unexpectedly, seemingly bypassing the newly configured authentication. Lin suspects a cached token from previous testing is the culprit. This is a great reminder that live demos, while exciting, can sometimes be unpredictable!

To overcome this, Lin attempts to reset the authentication state and use a private browser session. The crucial part of the demonstration is when the MCP Inspector is challenged for authentication. This is where the “auth dance” begins:

  1. Authentication Challenge: The Inspector is prompted to authenticate against the Keycloak realm.
  2. Client Registration: The “MCP Client” (pre-configured in Keycloak) is used.
  3. Authorization Flow: The user logs in, obtains an authorization code, and a token request is sent.

Unfortunately, the demo runs into further issues, and a successful connection after the authentication flow isn’t achieved within the allotted time.

  • Demo Hiccups: Caching tokens and unexpected authentication flows can complicate live demonstrations.
  • The Promise: Despite the technical glitches, the concept is clear: the gateway intercepts requests and enforces authentication and authorization policies defined in Keycloak.

The Power of the Gateway Approach 💪

Even with the demo’s unexpected twists, the core message is powerful. By placing an MCP gateway like Agent Gateway in front of your MCP server, you gain:

  • Decoupled Security: Keep your core application logic clean and focused.
  • Centralized Authentication: Manage authentication and authorization for multiple services in one place.
  • Rapid Iteration: Quickly update security policies without redeploying your applications.

Lin concludes by inviting attendees to connect on LinkedIn for further discussion and feedback, acknowledging the debugging effort from the audience.

  • Key Statement: The beauty of setting up a gateway in between is that it allows you not to modify your MCP code, where you can configure all whether it’s authentication and authorization, do the auth stuff through a gateway.

This session provides a valuable glimpse into a more efficient and scalable way to secure your MCP services, demonstrating the immense value of intelligent gateways in modern microservice architectures. ✨

Appendix