One Button, Every MCP Client

If you publish an MCP server today, the last mile to your users is a mess. You write out install instructions for Claude Desktop, then a different set for Cursor, then a deep link for VS Code, then a CLI command for Claude Code, then a config-file snippet with a different path on macOS versus Windows for Windsurf, Zed, Cline, Continue, Warp, and Kiro — and then someone opens an issue because the client they use is not on your list. Every provider is re-solving the same distribution problem, badly, in their README, and every one of them is drifting out of date the moment they hit publish.