IntegrationsResources
Atlassian
Jira, Confluence, and other Atlassian products via the official MCP server
Atlassian integration connects your agents to Jira and Confluence through Atlassian's official MCP server. A single resource covers both products.
Server URL: https://mcp.atlassian.com/v1/mcp
Setup
- Navigate to Resources and click Add Resource
- Select Atlassian from the catalog
- The resource is added with all tools and scopes pre-configured
Each user connects their own Atlassian account via OAuth when they first use an Atlassian tool. Navigate to Connections to manage linked accounts.
Atlassian uses Dynamic Client Registration (RFC 7591) — the gateway registers a per-organization OAuth client with Atlassian automatically on first install. Embedded and bring-your-own modes are not available for this resource. See Credential modes for how this compares to other catalog resources.
Available tools
| Tool | Description |
|---|---|
addCommentToJiraIssue | Add a comment to a Jira issue |
addWorklogToJiraIssue | Log work against a Jira issue |
atlassianUserInfo | Get information about the authenticated Atlassian user |
createConfluenceFooterComment | Create a footer comment on a Confluence page |
createConfluenceInlineComment | Create an inline comment on Confluence content |
createConfluencePage | Create a Confluence page |
createIssueLink | Create a link between two Jira issues |
createJiraIssue | Create a new Jira issue |
editJiraIssue | Edit fields on an existing Jira issue |
fetch | Fetch a Jira or Confluence resource by URL |
getAccessibleAtlassianResources | Get accessible Atlassian Cloud sites and their IDs |
getConfluenceCommentChildren | List child comments of a Confluence comment |
getConfluencePage | Get the full content of a Confluence page |
getConfluencePageDescendants | List descendant pages under a given parent page |
getConfluencePageFooterComments | List footer comments on a Confluence page |
getConfluencePageInlineComments | List inline comments on a Confluence page |
getConfluenceSpaces | List Confluence spaces |
getIssueLinkTypes | List available Jira issue link types |
getJiraIssue | Get a Jira issue by key or ID |
getJiraIssueRemoteIssueLinks | Get remote issue links on a Jira issue |
getJiraIssueTypeMetaWithFields | Get create-metadata fields for a Jira issue type |
getJiraProjectIssueTypesMetadata | Get issue types available in a Jira project |
getPagesInConfluenceSpace | List pages in a Confluence space |
getTransitionsForJiraIssue | List available transitions for a Jira issue |
getVisibleJiraProjects | List Jira projects visible to the authenticated user |
lookupJiraAccountId | Look up a Jira account ID by email or username |
search | Search across Jira and Confluence content |
searchConfluenceUsingCql | Search Confluence content using CQL |
searchJiraIssuesUsingJql | Search Jira issues using JQL |
transitionJiraIssue | Transition a Jira issue through its workflow |
updateConfluencePage | Update an existing Confluence page |
Required scopes
read:jira-work— read projects, issues, and commentswrite:jira-work— create and update issues, comments, and worklogsread:jira-user— read Jira user informationmanage:jira-project— manage project-level configurationmanage:jira-configuration— manage global Jira configurationread:confluence-content.all— read all Confluence content including pages and blog postsread:confluence-content.summary— read content summarieswrite:confluence-content— create and update Confluence contentread:confluence-space.summary— read space summaries and metadatawrite:confluence-space— modify space settingsread:confluence-user— read Confluence user informationread:confluence-groups— read Confluence group membershipread:confluence-props— read content propertieswrite:confluence-props— write content propertiessearch:confluence— search Confluence contentoffline_access— maintain access when the user is offline
Policy examples
- Allow read-only access: tool patterns
get*,search*,fetch,atlassianUserInfo - Block writes: add deny rules for
create*,edit*,update*,transition*,addCommentToJiraIssue,addWorklogToJiraIssueabove any allow rules - Allow full access for a specific agent: scope an allow rule for
*to agentclaude-codeon this MCP server