How do I avoid mixing TypeScript SDK v1 and v2 connection examples?
The official TypeScript SDK's stable v2 separates client and server packages, including @modelcontextprotocol/client and @modelcontextprotocol/server. The v1 @modelcontextprotocol/sdk line remains separately supported. A setup guide must distinguish those generations instead of rewriting an existing project's imports or dependencies. Montage is the remote server here; your application needs a compatible client transport and its own approved authorization path.
https://app.montages.co/mcpOn the authorized Streamable HTTP client, execute signals_status and inspect the actual workspace response. Report errors explicitly; do not start an agent or call write tools.Read the package boundary first
Inspect package.json, the lockfile and existing MCP imports to identify the SDK generation used by this application. For v2, consult the split client package documentation; for v1, stay with the supported v1 reference. Do not add a second generation to make a copied snippet compile, and do not replace unrelated server-side dependencies during this connection task.
Choose the client Streamable HTTP transport
Use the version-matched client transport for https://app.montages.co/mcp. The server package is for implementing servers, not a prerequisite for reaching Montage. Keep transport construction and client connection consistent with the same SDK generation. The endpoint snippet avoids suggesting that a v1 import path is a drop-in v2 API or that a stdio transport can use an HTTPS URL.
Implement the approved OAuth boundary
Review the SDK's OAuth helpers and configure the application-specific callback, storage and authorization lifecycle required by your environment. Helpers are not a guaranteed automatic login solution. Keep tokens out of browser bundles, repository files and model messages as appropriate to your architecture. If approved auth cannot be completed, return an explicit blocked state instead of an empty tool response.
Discover before exposing tools to an agent
Open the configured client connection, inspect available tools and select signals_status for the preliminary diagnostic. Keep client resources alive until the call settles and close them afterward through the version's documented lifecycle. A discovered tool definition confirms metadata access, not permission to execute it, and no model loop is needed to make that distinction.
Require authorized signals_status output
Call Montage signals_status through the configured client and inspect its actual workspace response. For auth errors, revisit the application's OAuth integration rather than mixing helper APIs across versions. For transport errors, verify the Streamable HTTP class, endpoint and connection lifecycle. Leave research or write tools unavailable until this check succeeds, and report the exact SDK generation whose path was verified.
Keep the boundaries clear.
- v2 uses split @modelcontextprotocol/client and /server packages; v1 remains a separate supported line.
- Do not rewrite project dependencies or mix client imports across SDK generations.
- OAuth helpers require application setup and do not certify automatic Montage login.
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-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.