Skip to main content
Connecting Atlassian to NOFire AI gives an investigation access to the issues, pages, projects, and service components in your Atlassian workspace. When something breaks, NOFire AI searches for the runbook, triages the ticket, and posts its findings back to the ticket. Authentication uses an Atlassian API token. OAuth 2.0 support is coming soon.
This integration connects through the Atlassian MCP server. NOFire AI calls the hosted endpoint of Atlassian. You do not run any infrastructure for it.
API token authentication is disabled by default on Atlassian’s MCP server. An organization admin must enable it first:
  1. Go to Atlassian Administration
  2. Select Apps → AI settings → Rovo MCP server
  3. In the Authentication section, turn API token on
See Atlassian’s MCP server settings for details on domain allowlists and IP restrictions.

​
What this enables

  • Find runbooks: search Confluence for documented procedures by alert name, service, or error pattern
  • Incident context: pull past Jira incidents and postmortems to inform current investigations
  • Ticket triage: assess and prioritize incoming Jira issues based on production signals
  • Add comments: post root cause analysis, investigation summaries, or status updates to Jira tickets

​
Prerequisites

  • An Atlassian account with read access to the Jira projects and Confluence spaces you want NOFire AI to read.
  • An organization administrator who can turn on API token authentication, as described in the warning below.

​
Step 1: Create an Atlassian API token

Generate an API token

  1. Go to Atlassian API Tokens
  2. Click Create API token
  3. Name it nofire and click Create
  4. Copy the token. You enter it in Step 2. Atlassian shows the token once.
The API token inherits your Atlassian account permissions. Use an account with read access to the Jira projects and Confluence spaces NOFire should be able to query.

​
Step 2: Add Atlassian connection in NOFire AI

Configure the connection

  1. Go to the Connections tab in the NOFire AI dashboard at my.nofire.ai and click Connect on Atlassian (MCP).
  2. Enter:
    • Name (e.g., engineering-jira)
    • MCP Server URL: https://mcp.atlassian.com/v1/sse
    • Auth Header: Authorization
    • Auth Value: Bearer <your-api-token>
  3. Click Save to test the connection and establish the integration
Once connected, NOFire AI can query your Jira projects and Confluence spaces during investigations and chat sessions.

​
Example queries

​
Runbooks

​
Ticket triage

​
Investigation documentation

​
Pattern analysis

​
Test the connection

  1. Open the Connections dashboard and make sure that the Atlassian connection status is READY. A connection that stays in an error state did not authenticate.
  2. Ask NOFire a question that needs a Confluence page or a Jira ticket you know exists, using one of the example queries below. An answer that names it confirms the connection works end to end.

​
Troubleshooting

API token authentication is still off on the Atlassian MCP server, or the auth value is missing the Bearer prefix.
The Atlassian account behind the token cannot read those projects or spaces.