stdio_server seems to have a similar problem:

import asyncio

from mcp.server.stdio import stdio_server


async def run():
    async with stdio_server() as (read_stream, write_stream):
        print("inside")
    print("outside")


if __name__ == "__main__":
    asyncio.run(run())

this prints inside and never exits.

One could argue that's per design since stdio_server is built to run indefinitely. For the stdio_client however, I think it makes sense to be able to start up the server, run a discrete task and then exit.

Can you check with most recent master if it's fixed. I think #325 already addresses the issue

@dsp-ant Same problem still.

The proposed fix #361 still works fwiw, but I understand it's a bit of a workaround and not addressing the underlying issue.

One could argue that's per design since stdio_server is built to run indefinitely. For the stdio_client however, I think it makes sense to be able to start up the server, run a discrete task and then exit.

I disagree, but can move that discussion to a different issue. For example, the server might want to exit if it gets an uncaught exception (the current bug I'm facing), but even in normal circumstances, it could be checked into your repo and you switch commits, so it needs to restart a different version. For the LSP, vscode-languageclient respawns the server when it exits.

#372 probably fixed this. it also adds a process.terminate() like #361