Beans for mcplog, roots and others / need for session context?

[maxandersen]

currently I have to add McpLog on every method - couldn't that be field or constructor injected?

how about Roots (#204) could it be an injected bean which is kept uptodate based on events.

would be useful to have some client info available - have a session/request scope notion for MCP?

[mkouba]

currently I have to add McpLog on every method - couldn't that be field or constructor injected?

Well, currently the MCP logger name (sent back to the client) is derived from the feature name, i.e. tool:myToolMethod. We could make the logger a @Dependent bean and derive the logger name from the declaring class but that's IMO less useful (esp. if you combine different features on one class). Also the internals would have to be rewritten a bit (not everything is now CDI bean).

how about Roots (#204) could it be an injected bean which is kept uptodate based on events.

I don't know about roots - need to read the spec first.

would be useful to have some client info available - have a session/request scope notion for MCP?

Yes, we could introduce the session context. However, for stdio a singleton/application scope serves the same purpose.

[maxandersen]

Yes, we could introduce the session context. However, for stdio a singleton/application scope serves the same purpose.

yes sure, but the hope is that the same code can work equally well independent of the protocol used.