RepoSense RS Monogram
RepoSensereposen.se
/llm.txtGitHub Repo
modelcontextprotocol icon

modelcontextprotocol/python-sdk

v2.3.0

Curated ai tools / ai-agent / ai-sdk / backend / ecosystem repository (modelcontextprotocol/python-sdk) tracked via conditional GitHub .atom polling.

COMPATIBLE
What is modelcontextprotocol/python-sdk?

mcp is an open-source library and developer tool in the modelcontextprotocol/python-sdk ecosystem. It removes the friction of wiring up raw HTTP requests, streaming parsers, and authentication boilerplate so developers can integrate AI capabilities in a few lines of code.

AI-AGENTnpm:mcpPythonreleases.atom
#ai-agent#ai-sdk#python-sdk
AI Executive Summary & Artifact Size Impact
Quick Summary: What Changed · What To Do · Upgrade Effort

It was >=2.5.0. The new max_sse_event_size option n. Drop-in upgrade. Migration: None.

Semver: MINOR·Manifest: package.json
Artifact Size Impactunavailable
Size Unavailable
Telemetry unmeasured for pre-release or source-only registry build
Breaking Changes, Release Highlights & Migration Snippet

Key Release Highlights (v2.3.0)

  • It was >=2.5.0. The new max_sse_event_size option needs it.
  • Nothing to do unless you pin httpx2 below 2.10.
  • @mcp.tool(), add_tool and Tool.from_function raise InvalidSignature, naming the tool and the problem.
  • Until now the server started, and 2026-07-28 clients silently dropped the tool from their listing.
Zero Breaking Changes Detected

Verified safe drop-in upgrade for mcp in package.json.

Copy-Paste Upgrade / Migration Snippet
npm install mcp@2.3.0

Ecosystem Compatibility Matrix & Verified Graph Warnings

TypeScript 5.xcompatible— Ships standard TypeScript declaration files without type regressions.

Zero-Noise Historical Release Timeline (1)

Format: [Core Change] + [Required Action] + [Migration Effort]
v2.3.0COMPATIBLE⚖️ Size Unavailable

It was >=2.5.0. The new max_sse_event_size option n. Drop-in upgrade. Migration: None.

Upgrade & Migration Q&A (modelcontextprotocol/python-sdk v2.3.0)

Direct Answers for Engineers & AI Agents

Is modelcontextprotocol/python-sdk v2.3.0 safe to upgrade in production?

modelcontextprotocol/python-sdk v2.3.0 is classified as COMPATIBLE (MINOR release). It was >=2.5.0. The new max_sse_event_size option n. Drop-in upgrade. Migration: None.

What breaking changes or compatibility risks exist in modelcontextprotocol/python-sdk v2.3.0?

No breaking API changes or peer dependency conflicts are recorded for modelcontextprotocol/python-sdk v2.3.0 in the RepoSense compatibility graph.

What is the bundle size impact of mcp v2.3.0?

Measured bundle size telemetry is currently unavailable for mcp v2.3.0; verify build output locally before deploying.

How do I upgrade mcp to v2.3.0?

Upgrade mcp to v2.3.0 by running "npm install mcp@2.3.0" and applying the migration steps: npm install mcp@2.3.0