Enabling multi-user OAuth flow for self-hosted remote MCP (like Atlassian-hosted remote MCP)

[bshibilov-sh]

Hi team,

We’re trying to replicate the behavior described in this Atlassian community post using our own self-hosted remote MCP server, which we currently host as an ECS service.

When using Atlassian’s hosted remote MCP at https://mcp.atlassian.com/v1/sse, users are automatically redirected to the OAuth 2.0 wizard, where they can authenticate and grant access. This per-user OAuth flow works great — each user is identified individually, and tokens are handled dynamically.

Our goal is to enable the same behavior in our self-hosted remote MCP, where:

• Users accessing the MCP (via Claude Desktop) are automatically redirected to the Atlassian OAuth wizard if they haven’t authenticated yet
• Each user goes through the OAuth 2.0 flow and obtains their own access token
• Those tokens are stored and scoped based on their Atlassian permissions (projects, spaces, etc.)
• Authorization is per user, not globally tied to the deployer

Currently, when setting up a remote MCP, the workflow relies on a one-time manual auth to obtain tokens. We’d like to know if the MCP codebase supports (or plans to support) this multi-user OAuth model for self-hosted deployments.

Is there a way to configure the app so that self-hosted remote MCPs behave the same way as https://mcp.atlassian.com/v1/sse, prompting each user with their own auth flow?

Any guidance or best practices would be appreciated!

Thanks in advance.