MCP100 verdict
Recommended official MCP SDK for Python when you need direct, first-party protocol support for building MCP clients or servers.
MCP100 Assessment
Editorial verdict
Reviewed September 11, 2026
Task Fit
Mapped
Developer workflows
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Evidence scope
24.4k MCP repository stars
217M Python SDK package downloads / 30 days
Repository identity: modelcontextprotocol/python-sdk
Package identity: mcp · version 2.2.0
Stars observed September 24, 2026 · Downloads observed September 24, 2026
Exact reviewed repository identity; current GitHub repository stars are eligible as repository-level adoption evidence.
Exact MCP-specific package identity verified against the reviewed canonical repository. SDK package consumption; not MCP-server adoption.
Publisher activity observed September 23, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed September 11, 2026
Evidence-backed setup
This profile has type-appropriate, source-backed setup rather than an MCP-server client connector configuration.
Type-appropriate, source-backed setup for this sdk profile.
Capability
Recommended official MCP SDK for Python when you need direct, first-party protocol support for building MCP clients or servers.
First-party Python protocol primitives for exposing MCP server capabilities.
First-party Python client primitives for connecting to MCP servers.
Use the current official SDK line for MCP negotiation, requests, notifications, and supported transports.
This is an SDK, not a fixed MCP server tool catalog.
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
Reviewed access
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
Related reviewed MCPs
Retrieve current library and framework documentation for coding agents.
Choose this instead if
Choose Context7 MCP instead if current library and API documentation inside coding agents.
Retrieve current library and framework documentation for coding agents.
Discover and run MCP servers through Docker's MCP gateway.
Choose this instead if
Choose Docker MCP Gateway instead if running multiple MCP servers behind one stdio connection.
Discover and run MCP servers through Docker's MCP gateway.
Work with repositories, issues, pull requests, and GitHub workflows.
Choose this instead if
Choose GitHub MCP instead if repository, issue, pull-request, and code context.
Work with repositories, issues, pull requests, and GitHub workflows.
reviewed-detail:official-mcp-python-sdk is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Python implementation of the Model Context Protocol (MCP)
The documentation lives at https://py.sdk.modelcontextprotocol.io/.
It has a Get started guide, What's new in v2, the API reference, and the migration guide.
The Model Context Protocol lets you build servers that expose data and functionality to LLM applications in a secure, standardized way. Think of it like a web API, but designed for LLM interactions. With this SDK you can:
Python 3.11+.
Create a server.py:
from mcp.server import MCPServer
mcp = MCPServer("Demo")
@mcp.tool()
def add(a: int, b: int) -> int:
"""Add two numbers."""
return a + b
@mcp.resource("greeting://{name}")
def greeting(name: str) -> str:
"""Greet someone by name."""
return f"Hello, {name}!"
Full example: docs_src/index/tutorial001.py
That's a complete MCP server: one tool, one templated resource. Open it in the MCP Inspector:
uv run mcp dev server.py
Call add with a=1, b=2 and you get 3 back.
Notice what you did not write: no JSON Schema (a: int, b: int is the schema), no request parsing, no validation code, no protocol handling. Two type-hinted Python functions and a docstring.
Get started takes it from here.
The same package is a full MCP client. Serve server.py over HTTP:
uv run mcp run server.py --transport streamable-http
then point a Client at it:
import asyncio
from mcp import Client
async def main() -> None:
async with Client("http://localhost:8000/mcp") as client:
result = await client.call_tool("add", {"a": 1, "b": 2})
print(result.structured_content) # {'result': 3}
asyncio.run(main())
A URL means Streamable HTTP, the transport you deploy. Client can also launch a local server as a stdio subprocess or take any custom transport; Clients has the rest.
We are passionate about supporting contributors of all levels of experience and would love to see you get involved in the project. See the contributing guide to get started.
This project is licensed under the MIT License. See the LICENSE file for details.