Skip to content

fix: constrain MCP SDK to supported major - #195

Open
parvahuja wants to merge 1 commit into
mainfrom
parv/mcp-sdk-v1-compat
Open

fix: constrain MCP SDK to supported major#195
parvahuja wants to merge 1 commit into
mainfrom
parv/mcp-sdk-v1-compat

Conversation

@parvahuja

@parvahuja parvahuja commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • constrain the optional MCP SDK to >=1.1,<2
  • prevent clean installs from selecting the incompatible MCP 2.x API
  • preserve the existing MCP 1.x minimum

Why

A fresh pympp[mcp] wheel install currently resolves MCP 2.0 and fails at import because its exception API changed. This is a compatibility patch only; it adds no MCP runtime or instrumentation behavior.

This is an independent prerequisite for #184.

Validation

  • full suite: 778 passed, 41 skipped
  • clean wheel with [tempo,mcp] resolves MCP 1.29 and imports the existing Tempo and MCP public surfaces
  • Ruff, formatting, Pyright, package build, and strict Twine validation pass

@socket-security

socket-security Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedpypi/​mcp@​1.29.099100100100100

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant