Skip to content

fix: cap mcp below 2 so a fresh install can start - #54

Open
Vishal Habib (vishalhabib99) wants to merge 1 commit into
microsoft:mainfrom
vishalhabib99:fix/cap-mcp-below-2
Open

Vishal Habib (vishalhabib99) wants to merge 1 commit into
microsoft:mainfrom
vishalhabib99:fix/cap-mcp-below-2

Conversation

@vishalhabib99

Copy link
Copy Markdown

Problem

pyproject.toml asks for mcp>=1.10.1 with no upper bound. mcp 2.x is now the latest on PyPI (2.3.0), and it removed mcp.client.streamable_http.streamablehttp_client (renamed streamable_http_client). src/mcp_interviewer/interviewer/connection.py imports the old name, so a fresh pip install mcp-interviewer, the install command in the README, gets mcp 2.3.0 and the CLI fails on import:

ImportError: cannot import name 'streamablehttp_client' from 'mcp.client.streamable_http'. Did you mean: 'streamable_http_client'?

Resolution today (uv pip compile, Python 3.12):

Requirement Resolves mcp to
mcp-interviewer (PyPI 0.0.12) 2.3.0, which breaks
this branch 1.30.0

uv.lock still pins mcp 1.10.1, so uv sync users and CI don't see this. Only pip and fresh resolutions do.

Change

mcp>=1.10.1,<2 in pyproject.toml and the matching requires-dist line in uv.lock. No locked versions change. Moving to the mcp 2.x client API can come later as a separate change.

Checked

  • mcp 2.3.0 has no streamablehttp_client in mcp.client.streamable_http. I checked this directly.
  • uv pip compile gives the resolutions in the table above.
  • pytest: 19 passed on this branch.

mcp 2.x removed mcp.client.streamable_http.streamablehttp_client, which
interviewer/connection.py imports. With mcp>=1.10.1 unbounded, pip install
mcp-interviewer now resolves mcp 2.3.0 and the CLI fails on import.
@vishalhabib99

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@vishalhabib99

Copy link
Copy Markdown
Author

Hi, just checking whether this one is on your radar. It's a small fix (cap mcp below 2 so a fresh install can start) and the branch is still mergeable. Happy to change anything.

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