We've implemented a complete OAuth 2.0 AuthProvider for direct SSE connections to MCP servers and would like to use it with https://mcp.atlassian.com/v1/sse.
Current Setup
✅ mcp-remote proxy works perfectly with our OAuth client
✅ AuthProvider loads same credentials from ~/.mcp-auth/mcp-remote-0.1.18/
✅ Implements full OAuth 2.0 flow with PKCE, token refresh, redirects
❌ Direct SSE connection returns HTTP 401 Unauthorized
Technical Details
Using the same OAuth client and tokens that work via mcp-remote proxy, but direct SSE connections fail with authentication errors.
Questions
1. Is the mcp-remote OAuth client restricted to proxy-only mode?
2. What's the process for direct SSE access approval?
3. Do we need different OAuth scopes/client configuration?
4. Is there a whitelist application process for enterprise integrations?
Could the Atlassian team provide guidance on enabling direct SSE access or point us toward the approval process?
