FastMCP.run(transport="stdio") produces noisy traceback on KeyboardInterrupt instead of clean exit

Initial Checks

• I confirm that I'm using the latest version of MCP Python SDK
• I confirm that I searched for my issue in https://github.com/modelcontextprotocol/python-sdk/issues before opening this issue

Description

Running a FastMCP stdio server from the terminal and interrupting with Ctrl-C produces a multi-frame traceback through anyio.run() → asyncio.runners → mcp.server.lowlevel.server.run → anyio.streams.memory.receive. The server is correctly waiting on stdin in an async loop; the trace surfaces because anyio/asyncio don't suppress the cancellation chain. Suggested fix: catch KeyboardInterrupt (or asyncio.CancelledError at the outer boundary) inside FastMCP.run and exit cleanly. Cosmetic but reduces user confusion when testing MCP servers from the terminal.

Example Code

Python & MCP Python SDK

Python 3.13.5
MCP Python SDK 1.27.1

先重現 FastMCP stdio 伺服器的 Ctrl-C 行為，接著追蹤 FastMCP.run 經過 mcp.server.lowlevel.server.run 以及 anyio 記憶體接收路徑的流程。修正完成的條件是：中斷伺服器時能夠乾淨地結束且不出現 traceback，同時正常的關閉行為維持不變。