fix: upgrade mcp to 1.26.0 and bump version to 1.82.5

[joereyna]

Summary

• Upgrades mcp from 1.25.0 to 1.26.0 in poetry.lock
• Bumps litellm version from 1.82.4 → 1.82.5 (patch release)

The pyproject.toml constraint (>=1.25.0,<2.0.0) already allows 1.26.0 — only the lockfile needed updating for the MCP upgrade.

Version bump is required as 1.82.4 is already published to PyPI and cannot be re-uploaded.

Test plan

• Verify MCP tests pass
• Verify PyPI publish succeeds with 1.82.5

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Mar 20, 2026 4:34am

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing joereyna:fix/upgrade-mcp-1.26.0 (32ada45) with main (30589b0)}

[greptile-apps]

Greptile Summary

This PR upgrades the mcp (Model Context Protocol SDK) optional dependency from 1.25.0 to 1.26.0 in poetry.lock, and bumps the litellm package version from 1.82.4 to 1.82.5 in pyproject.toml.

• The pyproject.toml version constraint (>=1.25.0,<2.0.0) already permits 1.26.0, so the upgrade is compatible.
• The dependency tree for mcp is unchanged between 1.25.0 and 1.26.0 (same transitive dependencies and version bounds), making this a clean, low-risk upgrade.
• The pyproject.toml change also bumps the litellm version from 1.82.4 to 1.82.5 and updates the commitizen version — this additional scope is not mentioned in the PR description.
• The test plan checkbox ([ ] Verify MCP tests pass) remains unchecked, providing no verification that the upgrade was validated.

Confidence Score: 4/5

• This PR is largely safe to merge — the mcp upgrade is a clean patch with no dependency tree changes — but the undocumented litellm version bump and the unchecked test plan reduce confidence slightly.
• The mcp dependency upgrade from 1.25.0 to 1.26.0 is low risk: the transitive dependency set is identical and the version constraint already allows 1.26.0. The main concerns are the unexplained litellm version bump in pyproject.toml (not covered by the PR description) and the unverified test plan.
• pyproject.toml — contains an undocumented version bump not described in the PR.

Important Files Changed

Filename	Overview
poetry.lock	mcp bumped from 1.25.0 to 1.26.0 with updated file hashes; the dependency tree for mcp is identical between the two versions, making this a clean, safe upgrade.
pyproject.toml	litellm package version bumped from 1.82.4 to 1.82.5 and commitizen version updated, but this scope is not mentioned in the PR description which claims only the lockfile was changed.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["pyproject.toml\nmcp >=1.25.0,<2.0.0"] --> B["poetry.lock\nResolved: mcp 1.26.0"]
    B --> C["mcp 1.26.0 Dependencies"]
    C --> D["anyio >=4.5"]
    C --> E["httpx >=0.27.1"]
    C --> F["pydantic >=2.11.0,<3.0.0"]
    C --> G["pydantic-settings >=2.5.2"]
    C --> H["pyjwt >=2.10.1 + crypto"]
    C --> I["starlette >=0.27"]
    C --> J["uvicorn >=0.31.1"]
    C --> K["typing-inspection >=0.4.1"]
    style B fill:#d4edda,stroke:#28a745
    style A fill:#fff3cd,stroke:#ffc107

Loading

_{Last reviewed commit: "fix: upgrade mcp to ..."}

[greptile-apps]

Undocumented version bump

The PR description says "only the lockfile needed updating," but pyproject.toml was also modified to bump the litellm version from 1.82.4 to 1.82.5 (along with the matching commitizen version). This is likely an automated release bump, but it is not acknowledged anywhere in the PR description. Please clarify whether this version bump is intentional and expected as part of this PR.

[greptile-apps]

No reviewable files after applying ignore patterns.