How do I qualify Go MCP OAuth support against the installed protocol path?
Go’s experimental OAuth boundaries require explicit qualification before an application attempts Montage account access. Match the installed module and protocol support to the required flow, preserving a safe blocked outcome instead of inferring universal compatibility from transport initialization or another client’s success. Protocol-qualified auth support is part of the client’s readiness boundary. A module may provide remote transport while its experimental authorization facilities remain unsuitable for the required flow, so an explicit unsupported result is preferable to speculative compatibility claims.
Help me qualify Go MCP OAuth support against the installed protocol path. Inspect go.mod and go.sum for the actual official SDK release and consult that version’s mcp and auth/oauthex documentation. State the installed release and actual response or capability blocker. No writes.Read module evidence
Inspect go.mod and go.sum for the actual official SDK release and consult that version’s mcp and auth/oauthex documentation. Do not fetch modules or assume repository-head examples describe the binary already deployed.
Identify the supported flow
Review the documented experimental limits and protocol-version qualifications relevant to the application. A remote Streamable HTTP client can exist even when its available auth helpers cannot satisfy the required account authorization path.
Keep authorization requirements intact
If the installed facilities cannot support approved access, return a clear unsupported state. Do not downgrade validation, forward an enterprise assertion speculatively or convert a handshake into an assumed private-workspace grant.
Test only a qualified path
With supported approved authorization, execute signals_status directly through the documented Go client lifecycle. No model or workspace write is necessary to verify the selected account’s ability to perform this one read.
Report protocol-qualified proof
State the installed release and actual response or capability blocker. A successful fallback in a proven interactive OAuth client may solve the user’s access need, but it cannot certify that the Go implementation completed the same flow.
Keep the boundaries clear.
- Do not downgrade validation, forward an enterprise assertion speculatively or convert a handshake into an assumed private-workspace grant.
- A successful fallback in a proven interactive OAuth client may solve the user’s access need, but it cannot certify that the Go implementation completed the same flow.
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.