mcp-oauth-provider-integ-when-integrating-a-third-party-oauth-identity-prov-98ddbb65

THEN Evaluate the two main strategies: (1) Direct exposure — list the external provider’s authorization and token endpoints in the MCP server’s OAuth metadata. This yields lower latency and simpler implementation but offers less control (e.g., cannot add state parameter if provider lacks it). (2) Proxy via local endpoints — hide the external provider behind the MCP server’s own OAuth endpoints and handle token exchange logic server-side. This gives full control but increases latency and complexity. For the proxy approach, implement or reuse a `ProxyOAuthServerProvider` pattern that accepts external endpoints and delegates token retrieval, as discussed in the issue. The choice depends on whether flexibility or simplicity is prioritized.

// ProxyOAuthServerProvider concept (TypeScript)
class ProxyOAuthServerProvider implements OAuthServerProvider {
  constructor(
    private externalAuthEndpoint: URL,
    private externalTokenEndpoint: URL,
    // ... other config
  ) {}
  // Implement required methods to forward requests to external provider
}