How should a Go application handle experimental OAuth support safely?
The official Go SDK provides MCP client functionality and an auth/oauthex package, but some OAuth support is experimental for particular protocol versions. That is a compatibility constraint, not permission to bypass authentication. Use this guide to qualify the existing application's client and auth path before attempting remote access. No universal OAuth parity or live-certified Montage connection is claimed for Go deployments.
https://app.montages.co/mcpWith approved auth and a supported protocol path, execute signals_status and inspect the real workspace result. On experimental OAuth incompatibility, stop and report blocked rather than bypassing auth.Pin the investigation to the installed module
Read go.mod and go.sum to identify the project's SDK release and consult that release's official documentation. Inspect the mcp and auth/oauthex facilities it actually provides. Do not fetch modules or change versions for this guide. Record relevant protocol-version limits before choosing an auth implementation, rather than assuming repository-head examples match the deployed binary.
Configure a remote HTTP client transport
Use the installed SDK's documented Streamable HTTP client connection with https://app.montages.co/mcp as its target. Keep transport initialization separate from account authorization so that diagnostics identify the failing layer. Do not create a local Montage server or substitute a different endpoint suffix to work around an authentication challenge returned by the real hosted service.
Evaluate OAuth support explicitly
Review experimental limitations in auth/oauthex against the protocol and authorization requirements of your environment. The application must own approved auth state, callbacks and private storage where applicable. If the supported path is uncertain or incompatible, fail closed and select a proven OAuth client for interactive access. Never interpret an enterprise identity assertion or a tool list as a replacement for Montage authorization.
Bound the connection and tool surface
Use the SDK's documented context and session lifecycle to initialize the client, discover tools and select signals_status. Keep cancellation and connection errors visible to the caller instead of retrying indefinitely or downgrading authentication. Avoid exposing the full discovered tool set to an agent before establishing that the intended account can make a single authorized read-only call.
Verify signals_status or report blocked
Execute Montage signals_status through the approved Go client and inspect the actual workspace result. If auth negotiation hits an experimental limitation, stop and document that boundary without certifying parity. For transport failures, check the SDK's HTTP support, endpoint and session lifecycle. No collection, write or paid model call should substitute for this final read-only check, and discovery alone must remain labeled as discovery.
Keep the boundaries clear.
- Some Go OAuth support is experimental and protocol-version-dependent; universal parity is not certified.
- Use the installed mcp and auth/oauthex documentation without downloading or changing modules here.
- Fail closed when authorization is unsupported; a proven OAuth client is the interactive fallback.
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.