---
title: "Atlassian MCP integration for LuumenAI"
url: "https://www.luumen.ai/integrations/atlassian-mcp/"
entity: SoftwareIntegration
category: "AI & automation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Atlassian MCP integration for LuumenAI

Read Jira, Confluence, and Compass for context; post updates as approved steps.

## What LuumenAI can do with Atlassian MCP

LuumenAI connects to Atlassian MCP with OAuth 2.0 and exposes 41 tools (27 read-only · 14 write). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: OAuth 2.0
- Tools available: 41 tools (27 read-only · 14 write)
- Plan: available on all plans
- Category: AI & automation

## About Atlassian MCP with LuumenAI

Connect the Atlassian MCP server and Luumen can read the issues, pages, spaces, and Compass components your team already works in. It pulls ticket detail and runbook pages to answer questions during an incident, then posts comments, worklogs, or new components as previewed steps you approve. Access follows your existing Atlassian permissions.

## Example tools

Read-only (27 in total):

- `ATLASSIAN_MCP_ATLASSIAN_USER_INFO` — Get current user info
- `ATLASSIAN_MCP_FETCH` — Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content
- `ATLASSIAN_MCP_GET_ACCESSIBLE_ATLASSIAN_RESOURCES` — Get cloudId to make tool calls.
- `ATLASSIAN_MCP_GET_COMPASS_COMPONENT` — Get a Compass component by ID
- `ATLASSIAN_MCP_GET_COMPASS_COMPONENTS` — Get a list of Compass components
- `ATLASSIAN_MCP_GET_COMPASS_CUSTOM_FIELD_DEFINITIONS` — Get a list of Compass custom field definitions
- `ATLASSIAN_MCP_GET_CONFLUENCE_COMMENT_CHILDREN` — Get reply(child) comments for a comment
- `ATLASSIAN_MCP_GET_CONFLUENCE_PAGE` — Get a Confluence page or blog post by ID, including body content.

Write and destructive (14 in total, approval required by default):

- `ATLASSIAN_MCP_ADD_COMMENT_TO_JIRA_ISSUE` — Add or update a comment on a Jira issue
- `ATLASSIAN_MCP_ADD_TEAMWORK_GRAPH_CONTEXT` — Adds a relationship between two entities in the Teamwork Graph (e.g.
- `ATLASSIAN_MCP_ADD_WORKLOG_TO_JIRA_ISSUE` — Add or update a worklog on a Jira issue.
- `ATLASSIAN_MCP_CREATE_COMPASS_COMPONENT` — Create a new Compass component
- `ATLASSIAN_MCP_CREATE_COMPASS_COMPONENT_RELATIONSHIP` — Create a relationship between Compass components
- `ATLASSIAN_MCP_CREATE_COMPASS_CUSTOM_FIELD_DEFINITION` — Create a custom field definition in Compass
- `ATLASSIAN_MCP_CREATE_CONFLUENCE_FOOTER_COMMENT` — Create a footer comment on a page or blog post
- `ATLASSIAN_MCP_CREATE_CONFLUENCE_INLINE_COMMENT` — Create an inline comment on specific text in a page or blog post.

## Frequently asked questions

### How does LuumenAI connect to Atlassian MCP?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Atlassian MCP on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default. Administrators configure that per tool.

### Is there an audit trail?

Every call to Atlassian MCP — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/atlassian-mcp/