From a6bd66aca897449ae55445449d43ff9ae69ed890 Mon Sep 17 00:00:00 2001 From: Stephan Eberle Date: Mon, 13 Apr 2026 19:43:19 +0200 Subject: [PATCH] docs: link fastmcp-keycloak-local companion project from Keycloak integration page (#3904) --- docs/integrations/keycloak.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/integrations/keycloak.mdx b/docs/integrations/keycloak.mdx index 163706573..22d61f132 100644 --- a/docs/integrations/keycloak.mdx +++ b/docs/integrations/keycloak.mdx @@ -60,6 +60,12 @@ async def get_access_token_claims() -> dict: **Production security**: Always configure the `audience` parameter in production. Without it, your server accepts tokens issued for any audience. Configure Keycloak audience mappers and set `audience` to your server's base URL to ensure tokens are specifically intended for your server. +## Local Development + +Local infrastructure tooling is deliberately kept out of the FastMCP core library to keep auth integrations slim and the associated maintenance burden as low as possible. That said, Keycloak is a popular identity provider for local development and testing, so a dedicated FastMCP-compatible setup blueprint lives in the companion project [**fastmcp-keycloak-local**](https://github.com/stephaneberle9/fastmcp-keycloak-local). + +It provides everything needed to develop and test FastMCP servers with Keycloak OAuth locally: a Docker-based Keycloak setup with a pre-configured `fastmcp` realm (Dynamic Client Registration enabled, test user included), cross-platform start scripts, and integration guides for the MCP Inspector, Claude Desktop, and Claude Code CLI. + ## Testing ### Running the Server