Re:MCP is eating the world–and it's here to stay
by ashwinsundar on Tuesday June 24, 2025 @06:38PM
(#44371788)
I would invite everyone to participate constructively in improving it.
How do you recommend that I participate? I've written a few MCP servers (based on FastMCP - great work!), and contributed one to Anthropic's list. How do I actually participate in maintaining or improving the core MCP spec? I was under the impression that it was being driven by Anthropic.
Re:MCP is eating the world–and it's here to stay
by lightbulbish on Tuesday June 24, 2025 @08:18PM
(#44372461)
IIRC they talk about it here
https://www.youtube.com/watch?v=m2VqaNKstGc&ab_channel=Laten...
TL;DR If you want to engage with the MCP protocol you can do so here. https://github.com/modelcontextprotocol
Re:MCP is eating the world–and it's here to stay
by yjp20 on Tuesday June 24, 2025 @06:45PM
(#44371852)
(author here)
You're right, that snippet was ai-generated and I forgot to action one of my todos to fix that snippet. This was negligent on my part, and I hope you'll forgive me.
We're fixing that right now, thank you for the correction!
Re:MCP is eating the world–and it's here to stay
by kibibu on Wednesday June 25, 2025 @07:44AM
(#44376154)
Is this response also ai-generated?
FastMCP exists because I found the original spec and SDK confusing and complicated. It continues to exist because it turns out there's great utility in curating an agent-native API, especially when so many great dev tools have adopted this client interface.
But the spec is still so young and at such risk of being co-opted by hype (positive and negative). I would invite everyone to participate constructively in improving it.
Lastly: this article is plainly AI generated, as `from mcp import tool` is completely hallucinated. Just some food for thought for the "AI should be able to figure out my complex REST API" crowd that seems well represented here.