Hi everyone,
We’re evaluating whether we can use Rovo as a “knowledge backend” behind an external chat (N8N + LLM), where the UI is ours but the Jira/Confluence context comes from Rovo.
From the docs, it looks like Rovo/MCP access is designed around interactive OAuth 2.x flows (browser login, user consent, short‑lived tokens) for clients like ChatGPT/Claude/IDEs, and we haven’t found any reference to:
- Rovo‑specific service accounts / service tokens / API tokens.
- OAuth `client_credentials` or similar machine‑to‑machine flows.
- Official patterns for server‑to‑server integrations (e.g. from N8N or another backend).
Concrete questions:
- Is there currently any supported way to use Rovo as a technical M2M service (via service accounts, API tokens, or `client_credentials`), or is it intentionally limited to usage within the Atlassian ecosystem (UI, Forge, Automation, official Slack/extension, etc.)?
- If not supported today, is there anything on the roadmap or any public feature requests to expose Rovo as an API consumable from external backends?
We’d really appreciate a clear confirmation so we can decide whether to keep trying with Rovo or build our own RAG/vector store instead.
Thanks in advance.