Skip to content

fix: pin bridge dependency mcp<2 — mcp 2.0.0 breaks fresh installs (#67) - #68

Merged
virtualsteve-exa merged 1 commit into
devfrom
fix/pin-mcp-1x
Aug 5, 2026
Merged

virtualsteve-exa merged 1 commit into
devfrom
fix/pin-mcp-1x

Conversation

@virtualsteve-exa

Copy link
Copy Markdown
Collaborator

Closes #67. Urgent: mcp 2.0.0 on PyPI removed streamablehttp_client from mcp.client.streamable_http; the bridge's PEP 723 pin was unbounded (mcp>=1.0), so every fresh uv environment resolution now crashes the bridge at import — i.e. all new installs are broken on main today. Existing installs coast on uv's path-keyed env cache, which is why nobody's machine caught it until the #66 path move forced a fresh resolve (its mystery "1 skipped").

  • Pin → mcp>=1.0,<2 (one line); AI BOM regenerated, now records the bound.
  • Verified in a fresh env: import succeeds, --check proceeds to the network stage; the no-creds smoke test un-skips and passes (6/6 in test_bridge_static.py).
  • mcp 2.0 API migration is deliberate follow-up work, not this PR.

Sequencing: this must release ahead of (or with) #66 — promoting #66 unpinned would invalidate every user's cached env simultaneously.

Governance impact

None. Dependency version bound only; guardrail wiring, permission tiers, and the governance gate are untouched.

🤖 Generated with Claude Code

…67)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Steve Wilson <steve.wilson@exabeam.com>
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