Secure Jira and Confluence access for AI agents

Through Atlassian, agents can search and read Jira issues and Confluence pages, and create or update them when your policies allow it — every call runs through your policies and is logged for audit. A single resource covers both products.

Server URL: https://mcp.atlassian.com/v1/mcp

Setup

1. Navigate to Resources and click Add Resource
2. Select Atlassian from the catalog
3. On Choose how to install Atlassian, click Per-org dynamic registration — the only mode Atlassian offers

Clicking that card installs the resource with all tools and scopes pre-configured; Atlassian then shows an Admin setup required dialog with a Setup guide button pointing at Dynamic client registration below, which you do need to complete.

Each user connects their own Atlassian account via OAuth when they first use an Atlassian tool. Navigate to Connections to manage linked accounts.

Credential modes

Atlassian uses Dynamic Client Registration (RFC 7591) only — the gateway registers a per-organization OAuth client with Atlassian automatically on first install. SecureAuth-app and Bring-your-own-app modes are not available for this resource.

See Credential modes for how this compares to other catalog resources.

Dynamic client registration

DCR itself is automatic — the gateway registers an OAuth client with Atlassian on first install with no admin action required. The one piece of admin setup Atlassian requires is allowlisting the gateway origin on the Rovo MCP server config. Without this step, end-user OAuth completes but tool calls fail at runtime.

Settings → Rovo → Rovo MCP server → Domains

In your Atlassian admin console at admin.atlassian.com, add your gateway origin to Your domains:

https://oauth.aisecurity.services.<region>.connect.secureauth.com/**

Replace <region> with your region (us, eu, aus). The /** suffix authorizes any path under that origin.

Available tools

Tool names are matched exactly by policy rules unless you use a wildcard, so copy them from here verbatim — and check the Available Tools card on the resource's Overview tab in the Agent Authority console for the authoritative list of what your install actually exposes.

Required scopes

• read:jira-work — read projects, issues, and comments
• write:jira-work — create and update issues, comments, and worklogs
• read:jira-user — read Jira user information
• manage:jira-project — manage project-level configuration
• manage:jira-configuration — manage global Jira configuration
• read:confluence-content.all — read all Confluence content including pages and blog posts
• read:confluence-content.summary — read content summaries
• write:confluence-content — create and update Confluence content
• read:confluence-space.summary — read space summaries and metadata
• write:confluence-space — modify space settings
• read:confluence-user — read Confluence user information
• read:confluence-groups — read Confluence group membership
• read:confluence-props — read content properties
• write:confluence-props — write content properties
• search:confluence — search Confluence content
• offline_access — maintain access when the user is offline

Policy examples

Rules are evaluated top to bottom and the first match wins; a call that matches no rule is denied. New rules are created at the top of the list, so create the rule you want evaluated last first.

• Read-only access: allow get*, search*, fetch, atlassianUserInfo, lookupJiraAccountId, then disable or delete your organization's seeded Allow all rule. The allow rule alone restricts nothing — createJiraIssue, editJiraIssue, transitionJiraIssue, and every other write tool keep matching Allow all. Removing it is org-wide, so add the allows everything else needs first; alternatively keep Allow all and use the deny recipe below.
• Block writes: add deny rules for create*, edit*, update*, transition*, addCommentToJiraIssue, addWorklogToJiraIssue above any allow rules.
• Allow full access for a specific agent: scope an allow rule for * to agent claude-code on this MCP server. This grants — it does not restrict other agents, who fall through to whatever rule matches next.

Next steps

• Create a policy — start from the read-only pattern in Policy examples above.
• Credential modes — see how DCR compares to the other modes catalog resources use.
• Give Claude read-only access to Jira — a worked policy for this exact resource.