[vishalhabib99]

Description

The shopping-concierge Dockerfiles run pip install --no-cache-dir -r requirements.txt, and these requirements files leave mcp without an upper bound, so a new image build now gets mcp 2.3.0. mcp 2.x removed what this code imports, so each one fails on import:

File	Import	Result on mcp 2.3.0
mcp_cart_tools/server.py, mcp_shopping_tools/serp_agent.py	from mcp.server import FastMCP	ImportError
supervisor_agent/gateway_client.py	from mcp.client.streamable_http import streamablehttp_client	ImportError (renamed to streamable_http_client)
kb-search-mcp/server.py	from mcp.server.fastmcp import ...	ModuleNotFoundError

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Changes Made

• Adds <2 to mcp in those four requirements.txt files. Moving to the 2.x API can be a separate change.
• case-management/agentcore_sars/app/SARAgent has the same open bound in pyproject.toml, but its uv.lock pins mcp 1.x, so I left it alone.

Testing

	fresh resolve (uv pip compile, Python 3.12)	at that version
main	mcp==2.3.0	those names are absent from the v2.3.0 tag
this branch	mcp==1.30.0	present in the 1.30.0 source

I also ran these in clean environments, and each works on mcp 1.30.0 and fails on 2.3.0: from mcp.server import FastMCP (ImportError), from mcp.client.streamable_http import streamablehttp_client (ImportError), from mcp.server.fastmcp import FastMCP (ModuleNotFoundError). I did not run the images end to end.

[vishalhabib99]

Hi, just checking whether this one is on your radar. New shopping-concierge image builds and the kb-search install now get mcp 2.3.0, and each fails on import. This caps mcp below 2 in those four requirements files. Happy to change anything.

[vishalhabib99]

Thanks @vivibui for reviewing and merging!