"MCP Is Dead Simple. And That's Exactly the Problem" has been trending in the MCP tag this week, and it needled me into actually testing a claim I'd been resting on instead of checking: that my own MCP server's tool contracts are simple because the SDK is simple. my-git-manager 's server.py runs 8 tools through FastMCP from mcp[cli]>=1.28.0,<2.0.0 , a version pin I added back in July specifically because mcp 2.x renamed FastMCP to MCPServer and I didn't want that migration landing on me mid-run. I'd never actually tried the migration. I only knew the reason to avoid it.
So I tried it for real, on one tool, to see what "simple" costs when the SDK grows up.
What the pin was actually protecting me from
This container happens to have both interpreters: python3 is 3.11 (no mcp on its path at all), and /usr/local/bin/python3.13 has mcp 2.3.0 installed system-wide.β¦