You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Kehrlann, I went through the current docs on main after #1329 landed to see what is already covered and what is still missing.
docs/client-modern.md already has a solid "Identity and Authorization" section covering HttpClientMcpTransport, requestCustomizer, authorizationErrorHandler, and why transports should be shared across users rather than client instances.
The main gaps left seem to be:
docs/client.md (the 2025-11-25 client page) does not have an authorization section yet showing how to wire McpSyncHttpClientRequestCustomizer / McpAsyncHttpClientRequestCustomizer with transportContextProvider (or contextWrite(McpTransportContext.KEY, ...) on async) on HttpClientStreamableHttpTransport.
docs/server.md shows addToolFilter under "Filtering the Tool Listing per Request" and notes that hidden tools can still be invoked directly, but stops short of showing the matching check in callHandler using exchange.transportContext().
docs/server-modern.md mentions contextExtractor under "HTTP Security", and we could add a short example showing how a McpSyncToolRepository / McpAsyncToolRepository reads ctx.transportContext() in both list and find (or inside the tool handler) to enforce permissions per caller, plus a quick note leading people to spring-ai-community/mcp-security when they are on Spring Boot.
I have worked extensively with OAuth2 and context propagation in Java MCP servers and would be happy to put together a PR for this if you'd like to assign it to me.
Activity
media-ctrl commentedon Nov 9, 2026
mohit32886 commentedon Nov 16, 2026
Hi @Kehrlann, I went through the current docs on
mainafter #1329 landed to see what is already covered and what is still missing.docs/client-modern.mdalready has a solid "Identity and Authorization" section coveringHttpClientMcpTransport,requestCustomizer,authorizationErrorHandler, and why transports should be shared across users rather than client instances.The main gaps left seem to be:
docs/client.md(the 2025-11-25 client page) does not have an authorization section yet showing how to wireMcpSyncHttpClientRequestCustomizer/McpAsyncHttpClientRequestCustomizerwithtransportContextProvider(orcontextWrite(McpTransportContext.KEY, ...)on async) onHttpClientStreamableHttpTransport.docs/server.mdshowsaddToolFilterunder "Filtering the Tool Listing per Request" and notes that hidden tools can still be invoked directly, but stops short of showing the matching check incallHandlerusingexchange.transportContext().docs/server-modern.mdmentionscontextExtractorunder "HTTP Security", and we could add a short example showing how aMcpSyncToolRepository/McpAsyncToolRepositoryreadsctx.transportContext()in bothlistandfind(or inside the tool handler) to enforce permissions per caller, plus a quick note leading people tospring-ai-community/mcp-securitywhen they are on Spring Boot.I have worked extensively with OAuth2 and context propagation in Java MCP servers and would be happy to put together a PR for this if you'd like to assign it to me.