mcp.run adaptation & integration

[nilslice]

great work! would love to see mcp.run integration too -- as all servlets hosted can be accessed locally via stdio or remotely via SSE.

we have an mcp client to call them which could be integrated here potentially:

https://github.com/dylibso/mcpx-py

happy to chat more and see what we could do together.

[grll]

Hey @nilslice thanks for your message, also very nice work on mcp.run.

Very happy to discuss as yes mcpadapt do not fix the issue of easing the run of the mcp server and you still need to have all dependencies for the MCP server correctly setup and so on...

if I understand correctly and sorry I am not very familiar with wasm, in the case of stdio: a servlet would run locally with the mcp server? (the dependency for that is node?)

Then you have a client mcpx-py that could communicate with it ?

SSE is also on the roadmap and could be added quite quickly based on the official mcp sdk, but since you also have authentication simple SSE support might not be enough for mcp.run ?

[nilslice]

You are correct about the SSE auth. We have a patch into the TS SDK to handle this:

modelcontextprotocol/typescript-sdk#109

I don't think the equivalent has been don't for the Python SDK yet.

[nilslice]

if I understand correctly and sorry I am not very familiar with wasm, in the case of stdio: a servlet would run locally with the mcp server? (the dependency for that is node?)

in the case of mcpx-py, there is actually no stdio transport - everything is done in-memory but still uses the protocol.

eventually, it's likely few will use the stdio transport to connect to locally running servers. the wasm approach actually lets users call tools via Mcp as if they were just library calls. but they can be managed at runtime - provided dynamically via mcp.run