Jira / Atlassian MCP server
Search and create Jira issues and Confluence pages from your AI agents.
About
Connect Tracecat to Atlassian to drive Jira tickets and Confluence runbooks from agents working alongside SOC analysts and on-call responders. You can search issues with JQL and open tickets the moment a SIEM alert escalates, attaching enrichment context as comments so the assignee has what they need on first read. From there, agents can pull the matching Confluence runbook, edit issue fields as the incident progresses, and post a final summary back to Jira with the audit trail your compliance team already relies on.
Setup
- 1
Sign in with OAuth
You'll authorize Tracecat to access Jira / Atlassian on your behalf. No API keys to manage.
- 2
Select the
Jira / Atlassiantile in the Tracecat MCP catalogOpen the
MCP catalogin your workspace, select theJira / Atlassiantile, and complete the OAuth flow. - 3
Enable
Jira / Atlassianin your agentIn your
ai.agentaction orAgents→toolstab, selectJira / Atlassianfrom theMCP integrationsdropdown.
Tools
getAccessibleAtlassianResources | List the Atlassian cloud sites the connected user can reach. |
searchJiraIssuesUsingJql | Search Jira issues with a JQL query and pagination. |
getJiraIssue | Fetch a single Jira issue with fields, comments, and history. |
createJiraIssue | Create a new Jira issue in a given project with summary, description, and fields. |
editJiraIssue | Update fields, status, assignee, or labels on an existing Jira issue. |
addCommentToJiraIssue | Post a comment on a Jira issue. |
searchConfluenceUsingCql | Search Confluence content with a CQL query. |
getConfluencePage | Retrieve a Confluence page with body, version, and metadata. |
createConfluencePage | Create a new Confluence page in a space with title and body. |
updateConfluencePage | Update the title or body of an existing Confluence page. |