Can I register my own MCP OAuth client for Atlassian Remote MCP?

[April Wang]

Is it or will it ever be possible to register my custom MCP client with atlassian, similar to 3LO?

I’m building a custom MCP client and want to talk directly to the Atlassian Remote MCP (https://mcp.atlassian.com/v1/sse) so I can use the Jira/Confluence tools from an application.

Using mcp-remote works fine (browser pops, loopback callback, tools load). But when I try the same PKCE flow from my own Python client—using a 3LO (auth.atlassian.com) client ID—the token call against the MCP auth server (discovered from its well-known metadata) fails. So it seems like my client isn’t recognized by the MCP auth server.

Questions:

• Can I get a custom MCP client registered (like 3LO, but for mcp.atlassian.com)? If yes, how?
• Are redirects loopback-only (http://localhost:{port}), or can I request a public HTTPS redirect (for AKS/server use)?
• Should MCP clients be public PKCE (no secret), or can they be confidential?
• Is dynamic client registration supported?

[Dr Valeri Colon _Connect Centric_]

@April Wang Right now you can’t register your own OAuth client for the Atlassian Remote MCP server. Only Atlassian-approved MCP clients are allowed, and the MCP auth server won’t issue tokens to 3LO apps. No public client registration, no confidential-client flow, and no dynamic registration. Redirects are limited to loopback for the preview. Atlassian hasn’t announced plans to open this up yet.

[Trisha Griffis]

Q:Can I register my own custom MCP OAuth client (similar to a 3LO app) with Atlassian to use the Remote MCP Server?

A: Not currently. Atlassian’s Remote MCP Server is in public beta and only supports a curated set of MCP-compatible clients like Claude, VS Code, Cursor, etc.
 

Q: Will redirect URLs outside of localhost work—like a public HTTPS callback (e.g., on AKS/server)?

A: No. Atlassian currently whitelists only localhost-based redirect URIs or those used by their approved clients. External domains aren’t supported at this time.
 

Q: Should MCP clients be public (PKCE without secret) or confidential (with client secret)?

A: The documentation doesn’t specify or support registering custom OAuth clients yet. So the expected auth model for the approved clients remains internal and undocumented for custom use at this stage.

Q: Is dynamic client registration supported?

A: Not by Atlassian’s Remote MCP Server. While the MCP authorization spec (open MCP implementations) anticipates dynamic client registration, this is not supported in the Atlassian-hosted Remote MCP Beta.

If you have additional questions feel free to book time with us, we'd be happy to support you through it. We are an Atlassian Gold Solutions Partner, Jer-nee Consulting, you can schedule with us here.