MCP Python SDK

license

MIT(OSI)

source

public

core features withheld

no

The MCP Python SDK is released under the plain MIT License, and PyPI classifies the `mcp` package the same way, while the specification repository, the TypeScript SDK and the Inspector have moved to the project's Apache-2.0 transition terms. The whole SDK is in the public repository and installs from PyPI with no key or paid tier.

• https://github.com/modelcontextprotocol/python-sdk recorded 2026-08-13

  Repo page, 24,000 stargazers. The whole SDK is in the tree; install is `uv add "mcp[cli]"` with no key. No enterprise directory, second license or paid tier.

• https://pypi.org/project/mcp/ recorded 2026-09-28

  The PyPI page for `mcp` carries the classifier "OSI Approved :: MIT License" and states "This project is licensed under the MIT License."

• https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/LICENSE recorded 2026-09-28

  The raw LICENSE file is still the plain MIT License, "Copyright (c) 2024 Anthropic, PBC", with no Apache-2.0 transition preamble.

• https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md recorded 2026-09-28

  The README install line is uv add "mcp[cli]", and it states "This project is licensed under the MIT License." Searched the body for pricing, paid, subscription, license key, premium and hosted: none.

Adoption is measured as PyPI downloads of the `mcp` package. The listing is confirmed first-party rather than a squatted name: PyPI gives its repository as github.com/modelcontextprotocol/python-sdk and credits Model Context Protocol, a Series of LF Projects, LLC, as the author.

• https://pypistats.org/api/packages/mcp/recent recorded 2026-08-12

  333,111,291 downloads in the trailing 30 days for mcp

The SDK supports both roles, the full set of tools, resources and prompts, and every standard transport, against the 2026-07-28 specification. Unlike the official Go and Rust SDKs, its documentation does not enumerate the optional features - sampling, roots and elicitation - though the gap may be a documentation omission rather than a missing implementation.

• https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md recorded 2026-09-17

  The README states the coverage in one sentence each: "Build MCP servers that expose tools, resources, and prompts to any MCP host", "Build MCP clients that connect to any MCP server", "Speak every standard transport: stdio, Streamable HTTP, and SSE".