Back to timeline

Thu, October 1506:30ToolsMCP & SkillsInfra & costMCP & Skills guide

Official MCP Python SDK v2 released, supporting three transports and typed tool definitions

Decision Brief

What changedThe official Model Context Protocol Python SDK v2 is out, offering type-annotation-based server and client development with stdio, Streamable HTTP, and SSE transports.
Why it mattersPython type annotations generate JSON Schema directly, eliminating hand-written schema and request parsing, reducing MCP server and client work to a dozen lines of code.
Who should careAI coding tool users, Agent builders
Affected stackMCP
Builder actionUpdate MCP to the latest version
Source confidenceHigh · Official release / blog / repo

The SDK requires Python 3.11+ and installs via uv add "mcp[cli]" or pip install "mcp[cli]". The cli extra adds mcp dev, mcp run, and mcp install commands; install plain mcp if unneeded. On the server side, @mcp.tool() and @mcp.resource() decorators define tools and templated resources, with annotations like a: int, b: int acting as JSON Schema while the SDK handles request parsing, validation, and protocol handling. A full server with tools and resources fits in 15 lines, debuggable via mcp dev in MCP Inspector. For Python developers connecting LLM apps to external data and capabilities, the repetitive work of writing schemas, parsing requests, and wiring protocols is largely gone, cutting integration cost to one or two functions plus a docstring. Official support for stdio, Streamable HTTP, and SSE means existing MCP servers in other languages or custom protocols need no transport-compatibility rewrites. The SDK is MIT-licensed, with docs covering v2 features and a migration guide for teams on older versions.

Summary basis: full article readCompiled from the source scope noted above; the original remains authoritative.

Sources

Related intel

留言

登入后即可留言,和其他 builder 交换实测心得。

还没有留言,抢头香。