Re: Discussing the Decision to Not Make FastMCP the MCP Python standard

[gitanon112]

I am curious what is behind the incredible lag/refusal to make fastmcp the python standard? In all honesty, this repo has been plagued by incredible slowness to update, lack of responsiveness to the community, and I am curious why @jlowin from fastmcp) is completely absent from the contributors/release notes?

As someone extensively using MCP since its inception and working at (what I'd like to think) is the cusp of groundbreaking AI, FastMCP is superior in every way to whatever nonsense has plagued this repo. This repo, and MCP as a whole (IMHO) would benefit massively from simply making FastMCP the standard, rather than endless discussions in the specifications repo, entertaining the opinions of obsolete figures and non-forward thinking coders.

[dsp-ant]

I am not sure what specific lag/refusal you are referring to. If you prefer FastMCP from Jeremiah, please use that. Otherwise we are open for specific suggestions, and PRs and bugfixes to the Python SDK.

[gitanon112]

yes i apologize for this comment I made a while ago, came from a place of frustration. Since then, I have come to realize that the issue is more nuanced, open-source is hard, and both this repo and FastMCP have their tradeoffs. I appreciate your measured response to my ragepost, thanks.