Jira & Confluence
What your agent can do
Section titled “What your agent can do”Jira: list/search/read/create/update issues, add comments, query with JQL
Confluence: read pages and spaces, create and update pages, search content
Connecting Atlassian
Section titled “Connecting Atlassian”- Go to Console → Integrations → Jira & Confluence
- Click Connect Atlassian
- Select your Atlassian site (e.g.,
yourcompany.atlassian.net) - Approve the permissions → click Accept
One connection grants access to both Jira and Confluence for that site.
If your Atlassian admin blocks the Authorize step
Section titled “If your Atlassian admin blocks the Authorize step”Atlassian organisations control which third-party domains may use the Atlassian Rovo MCP server — the hosted MCP server your agents call. Newly created organisations have this on, so the first person to try Authorize sees Atlassian’s own consent screen refuse:
Your organization admin must authorize access from this redirect URL to this site.
Nothing is wrong with your connection. Atlassian stopped the approval before it ever reached Auteryn, which is why there is no error to retry here.
The fix. An org admin adds our domain in Atlassian Administration → Rovo → Rovo MCP server → Domains → Add domain:
https://console-api.auteryn.ai/**Add it once per environment — each is a separate entry. The field takes a
pattern, not a callback URL: a protocol is required, and the /** suffix is
optional but recommended so the entry covers every path at or below that
domain. Auteryn shows the exact value to paste under Blocked by your admin?
next to the Authorize button, so you can send it to an admin before anyone hits
the error.
If it still refuses right after the domain is added, Atlassian’s own troubleshooting is to delete the entry and re-add it — the admin UI can show a domain that has not yet reached the enforcement service — then retry in a private browser window to clear the cached consent.
Two things worth knowing:
- This blocks Authorize, not Connect Atlassian. Connecting sets up the Jira and Confluence APIs; Authorize is a second, separate approval that lets agents use Atlassian’s hosted MCP server. Until the domain is allowed, the connection keeps showing Auth needed → Authorize.
- The Allow Atlassian supported domains toggle on that page covers AI tools Atlassian partners with. It does not cover your own domains, which is why this entry is needed even with that toggle on.
Reference: Control Atlassian Rovo MCP server settings · Domain patterns · Fix OAuth consent block
Whose account does it act as?
Section titled “Whose account does it act as?”Connecting Atlassian signs in with your own account, so the connection is Personal · you — private to you by default. Share it from the connection card (Who can use this), or let each teammate act as themselves: on an internal agent, turn on Acts as each user for Jira/Confluence and everyone connects their own Atlassian login.
Example tasks
Section titled “Example tasks”Jira
- “List all open bugs assigned to me in the BACKEND project”
- “Create a Jira issue: ‘Fix login timeout’, priority High, project BACKEND, assigned to john@acme.com”
- “Move issue BACK-423 to ‘In Progress’ and add a comment”
- “Find all P1 issues open for more than 7 days”
Confluence
- “Find the Confluence page about our deployment process”
- “Summarize the ‘API Design Guidelines’ page in our Engineering space”
- “Create a Confluence page in Engineering titled ‘Incident Report - April 1’”
- Include the Jira project key and required fields in your agent’s instructions for issue creation workflows
- Combine with Slack: Slack alert → agent creates Jira issue → posts issue link back to Slack