Configuring an upstream MCP server that uses OAuth requires registering a redirect/callback URL in the provider's OAuth app. Atryum does not tell the user what that URL is, so they guess (for example "is it http://localhost:8080?"), register the wrong value, and authorization then fails or the Reconnect step stalls. The correct callback URL is effectively undiscoverable without reading the source or asking someone.
Success: the exact redirect URL Atryum expects is shown at the point where the user configures the OAuth server (and in the docs), ideally copyable, so OAuth setup works on the first attempt.
Configuring an upstream MCP server that uses OAuth requires registering a redirect/callback URL in the provider's OAuth app. Atryum does not tell the user what that URL is, so they guess (for example "is it http://localhost:8080?"), register the wrong value, and authorization then fails or the Reconnect step stalls. The correct callback URL is effectively undiscoverable without reading the source or asking someone.
Success: the exact redirect URL Atryum expects is shown at the point where the user configures the OAuth server (and in the docs), ideally copyable, so OAuth setup works on the first attempt.