Align stdio shutdown sequence with spec

[davenpi]

Align the stdio shutdown sequence with the MCP spec: close the server’s input, wait for exit, send SIGTERM if needed, and SIGKILL as a last resort.

Motivation and Context

The MCP spec recommends a careful shutdown sequence for stdio transport to avoid leaving orphaned or stuck server processes. This change follows those steps, making shutdowns more reliable and predictable.

How Has This Been Tested?

All tests pass (except one unrelated skipped test).

Breaking Changes

None

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation update

Checklist

• [x] I have read the MCP Documentation
• [x] My code follows the repository's style guidelines
• [x] New and existing tests pass locally
• [x] I have added appropriate error handling
• [x] I have added or updated documentation as needed

Additional context

None

[davenpi]

Hey @ihrpr! Do you have a sec to review this PR? It makes the SDK follow the stdio shutdown procedure to the letter!

[ihrpr]

related PR: https://github.com/modelcontextprotocol/python-sdk/pull/555

[felixweinberger]

Thank you again @davenpi for submitting this PR.

I spent yesterday and today trying to unify all the different approaches and fixes we have pending in this process termination space at the moment, as there are several interrelated fixes that either conflict or depend on each other - specifically #555, #729, #765, and #850.

I've added your change to #1044 as a draft with you as a co-author + added extensive regression testing. Would you be OK with consolidating this change into #1044 for the comprehensive testing & process handling introduced there?

[davenpi]

Thanks @felixweinberger for taking the time to coordinate all this! Consolidation sounds good.

[ihrpr]

Thank you @davenpi! Will close this one and we can continue in #1091