How do I audit TypeScript SDK package generations before connecting Montage?
The TypeScript SDK’s v2 package split and supported v1 line are different integration boundaries. Audit imports and package ownership before copying remote connection code, keeping a client-only task from becoming an unnecessary server dependency migration or an unsupported mix of OAuth helpers. Read package roles and imports together before selecting transport code. The split v2 client package and supported v1 line require coherent examples, and outbound Montage access should not become an unrelated server-hosting dependency migration during diagnosis.
Help me audit TypeScript SDK package generations before connecting Montage. Inspect package.json, the lockfile and existing MCP imports to identify the installed generation. Report the path tested and real workspace result or error, leaving the other generation unverified. No writes.Read manifest and imports together
Inspect package.json, the lockfile and existing MCP imports to identify the installed generation. A server package elsewhere in the workspace does not prove this application contains a compatible client or the same transport API.
Map package roles
For v2, distinguish @modelcontextprotocol/client from @modelcontextprotocol/server. For v1, use its separately supported reference. Reaching Montage is outbound client work and should not require adding hosting components just because a server example appears nearby.
Keep the connection coherent
Choose transport construction and client methods from the same generation’s documentation. Do not retain a v1 import beside a v2 helper as a speculative compatibility bridge, and do not change unrelated package boundaries during this audit.
Validate without inference
After approved application auth, open the documented Streamable HTTP client and execute signals_status directly. An import that typechecks or a definition returned by discovery cannot prove that account-scoped workspace execution completed.
Record the actual generation
Report the path tested and real workspace result or error, leaving the other generation unverified. This audit does not authorize dependency replacement or certify every future SDK release against the existing Montage application.
Keep the boundaries clear.
- Do not retain a v1 import beside a v2 helper as a speculative compatibility bridge, and do not change unrelated package boundaries during this audit.
- This audit does not authorize dependency replacement or certify every future SDK release against the existing Montage application.
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.