Leverage one MCP server process across multiple SDK sessions

[patniko]

For using stdio MCP servers with the SDK: unlike the experience in the VSCode github copilot experience that one MCP server instance serves all the sessions, in node.js SDK, each session will start its own running instance of the stdio MCP server process, which is not very ideal. Would be nice to use one MCP server process across multiple sessions.

[github-actions]

Thanks for opening this issue, @patniko!

This is a great enhancement suggestion. I've labeled this as enhancement and sdk/nodejs since it specifically relates to the Node.js SDK's handling of stdio MCP server processes.

The request to share a single MCP server process across multiple SDK sessions (similar to the VSCode experience) makes sense for resource efficiency.

AI generated by Issue Triage Agent