How do I review Python MCP SDK imports before migrating Montage code?
The Python SDK’s current Client interface should not be mixed blindly with older ClientSession recipes. Qualify the existing application’s installed generation before adapting code, and keep dependency changes outside a transport or authorization diagnostic unless separately approved. The installed package decides whether the current v2 Client example applies. A remote endpoint remaining stable does not mean old ClientSession imports, new constructors and generation-specific authorization helpers can be combined without reviewing their contracts.
Help me review Python MCP SDK imports before migrating Montage code. Compare the manifest, lockfile and current imports to identify the mcp package generation actually used. Report the installed generation and actual workspace result or blocker. No writes.Read installed evidence
Compare the manifest, lockfile and current imports to identify the mcp package generation actually used. Repository main documentation may describe a newer API than the deployed environment, so record the installed boundary rather than assuming parity.
Match the official reference
For compatible v2, use the documented Client from mcp interface and async URL lifetime. An older application may legitimately require different primitives; do not paste a v2 constructor into it merely because the hosted Montage endpoint is unchanged.
Keep generations coherent
Review transport construction, discovery and call_tool usage as one version-qualified path. Do not add a second API generation or remove existing application authorization just to make an isolated example resemble current documentation.
Inspect direct execution
With supported approved auth configured, discover signals_status and execute it inside the documented lifetime. A compiling import or successful constructor does not establish transport initialization, private account access or the correctness of later tool calls.
Document qualified proof
Report the installed generation and actual workspace result or blocker. Leave other SDK generations unverified, and do not represent this narrow diagnostic as approval to upgrade dependencies or rewrite the application’s unrelated MCP integration.
Keep the boundaries clear.
- Do not add a second API generation or remove existing application authorization just to make an isolated example resemble current documentation.
- Leave other SDK generations unverified, and do not represent this narrow diagnostic as approval to upgrade dependencies or rewrite the application’s unrelated MCP integration.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.