Hello Atlassian Community,
We are working with the Atlassian Rovo MCP Server and want to integrate it with GitHub custom agents running in GitHub Actions. However, we’ve encountered a major limitation: the MCP Server requires an interactive browser-based OAuth 2.1 login, which is not supported in headless CI/CD runners.
Could you please advise if there is a recommended solution or workaround to enable OAuth authentication and MCP connectivity in fully headless environments like GitHub Actions? For example, support for non-interactive OAuth flows, token injection, or managed persistent MCP proxies.
Any guidance or guidance on best practices would be greatly appreciated.
Thank you!
Hi @Pandithdurai Govindaraj
This document can answer all your questions.
I hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.