The mcp-remote proxy, used to connect desktop IDEs (VS Code, PyCharm, NeoVim, etc.) to the Atlassian MCP Server, currently has a hardcoded OAuth callback behavior that defaults to localhost.

Many enterprise organizations have strict IT security policies that prohibit local loopback redirects (localhost or 127.0.0.1) for OAuth flows. This prevents these organizations from authorizing and using Atlassian Rovo MCP features in their local development environments.

Proposed Change:

• Update mcp-remote to allow users to specify a custom callback URI via a command-line argument or configuration file.

• Provide a mechanism to support Fully Qualified Domain Name (FQDN) callbacks to satisfy enterprise security requirements.

• Improve documentation on how to implement a non-localhost authorization flow for headless or restricted environments.