Add integration-tests where a secured MCP server can be launched and tested

[sberyozkin]

I'm not sure it is a valid request, I'd like to have an integration test where we can have an MCP server launched, and I can send some tokens to it to verify how they are protected, to check OIDC protected resource metadata.

I see https://github.com/quarkiverse/quarkus-mcp-server/tree/main/transports/http/integration-tests, is it where it should be done ?

[sberyozkin]

Just to clarify, I'd only like to have, as a result of this issue, assuming it is agreed upon, a top level integration-tests folder with some basic-mcp-http-server integration test, which, when run, launches MCP server as per appication.properties and a test runs that calls that MCP server remotely.

And then I'll copy and paste a basic-mcp-http-server into some OIDC specific MCP server setups.

I can definitely add it to https://github.com/quarkiverse/quarkus-mcp-server/tree/main/transports/http/integration-tests, but there will be a few more dependencies, starting from quarkus-oidc - please close this issue if it is what you'd like me to do

[mkouba]

@sberyozkin Hm, couldn't we just add an integration test to the secure-mcp-sse-server sample app?

[sberyozkin]

Hi @mkouba I'm not sure it can qualify as an evidence, that demo assuming GitHub login too, Keycloak in devmode only.

We also have another demo with multiple MCP endpoints, based on Keycloak, that I can add tests too, but likewise, I'm not sure it can qualify as an evidence that a Quarkus MCP Server and OIDC combination offers a complete support for the server related parts of the MCP Authorization spec.
The spec probably has a few points that are not covered by the demo, they will be adding new things, and I'm not sure that demo is flexible enough to keep covering all of those spec points

[mkouba]

@sberyozkin Ok, I see. Feel free to create a top level integration-tests then.

[sberyozkin]

Thanks @mkouba, sure, I'll give a try next week and ping you