Conversation
jbouder
approved these changes
Jul 6, 2026
jbouder
left a comment
Contributor
There was a problem hiding this comment.
Amazing work, thank you! Approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per title. We can just use the default
pydantic_ai.mcp.MCPToolset, but we have to add authentication on top of it. Assuming the MCP server validates incoming requests for a bearer token from any OpenID provider, we need two separate auth lanes:This PR implements this scheme with an impersonating service account that has static credentials and is allowed to exchange its own credentials for any registered user.
On Keycloak this is a client with service account roles
and the service account having the
impersonationroleA valid config can look like
where
IMPERSONATOR_CLIENT_IDandIMPERSONATOR_CLIENT_SECRETare the static credentials of the Keycloak client above.