I wish they'd done a smaller launch of it and gather feedback rather than announcing a supposed new standard which feels a lot like a wrapper.
This here is atrocious https://github.com/modelcontextprotocol/quickstart-resources... It includes this mcp PyPI package which pulls in a bunch of other PyPI dependencies. And for some reason they say "we recommend uv". How is that related to just setting up a tool for an AI to use?
Compare that to this get weather example: https://api-docs.deepseek.com/guides/function_calling/
It makes me not want to use Claude/Anthropic.
The pyproject.toml in the Model Context Protocol example is just showing the new, "best" way to distribute and install Python projects and dependencies. If you haven't used uv before, it makes working with Python projects substantially better.
The Model Context Protocol server lets the model autonomously use the tool and incorporate its result. It's a much cleaner (imo obviously) separation of tool definition and execution.
but yes, it's the strongest anti-developer move to not directly support MCP. not surprised given OpenAI generally. but would be a very nice addition!