# Atlassian (Jira & Confluence) MCP for AI Agents AI Agent Connect

> Atlassian (Jira & Confluence) MCP connects your AI agent to your team's project management and documentation hub. It lets your agent read Jira issues, manage active sprints, and pull content from Confluence pages. Stop switching tabs between your code editor and your project boards; your agent handles the heavy lifting of finding info and updating statuses.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_4C51G3YFBR6QZGObvjzYxf2HTyIK8zjnkSC7foXq/ai-agent-connect
- **Tags:** agile-boards, issue-tracking, wiki, sprint-management, bug-tracking, team-collaboration

## Description

Imagine you're in the middle of a deep coding session and you need to know the specific requirements for a bug you're fixing. Usually, that means Alt-Tabbing out of your IDE, opening Jira, searching for the ticket, and then heading over to Confluence to find the technical spec. This Connector changes that. It turns your AI agent into a direct navigator for your entire Atlassian workspace. You can ask your agent to find a specific epic, summarize the status of a sprint, or pull the latest documentation for an API directly into your chat window. It bridges the gap between your active work and the documentation that supports it. By connecting this to the Vinkius catalog, you get a reliable way to keep your team's data in sync without the manual overhead of constant dashboard hopping. Your agent becomes a teammate that actually knows where the information is buried, so you can stay focused on the work that matters.

## Tools

### get_page
Pull the rich text content of a Confluence page into your conversation. This brings the actual documentation into your chat.

### list_projects
Get a list of all Jira projects to find the right keys for your queries. This helps you orient your agent within your organization.

### search_issues
Find specific Jira tickets using JQL queries. You can filter by status, priority, or assignee to find exactly what you need.

### get_issue
Pull the full details of a specific Jira ticket using its exact key. This gives your agent the full context of a single task.

### list_boards
See all agile boards available in your Jira instance. Use this to identify the correct workspace for your sprint queries.

### list_sprints
View all sprints for a specific board. This is useful for checking historical progress or current iteration tasks.

### get_myself
Retrieve your own authenticated user information from the Atlassian account. It helps the agent understand your permissions.

### list_spaces
See all Confluence spaces. This helps your agent navigate your team's entire documentation library.

### search_content
Use CQL to search through all Confluence content for specific keywords. It finds documentation across your entire wiki.

## Prompt Examples

**Prompt:** 
```
What's the status of the login bug?
```

**Response:** 
```
I've checked the Jira issues and found `AUTH-123`. It's currently `In Progress` and assigned to Sarah. The latest comment says they're waiting on the API key from the backend team.
```

**Prompt:** 
```
Find the documentation for the new onboarding flow.
```

**Response:** 
```
I found two relevant pages in Confluence: 'User Onboarding v2' and 'Internal Training Guide.' Would you like me to pull the content for 'User Onboarding v2'?
```

**Prompt:** 
```
Show me the current sprint for the mobile app project.
```

**Response:** 
```
The 'Mobile App' project is currently running 'Sprint 14'. There are 22 open tasks, with 5 marked as 'Blocked'. Here is the breakdown of the remaining items:

| Task ID | Title | Status |
|---|---|---|
| MOB-45 | Fix Auth Header | In Progress |
| MOB-46 | Update Styles | Blocked |
```

## Capabilities

### Search Jira issues with JQL
Find specific tickets based on status, priority, or assignee using complex queries.

### Retrieve Confluence page content
Pull the full text of a wiki page directly into your conversation for immediate context.

### View agile boards and sprints
See your active boards and current sprint progress without leaving your AI client.

### Browse projects and spaces
Discover all available Jira projects and Confluence spaces in your organization.

### Access user identity mappings
Automatically identify the current authenticated user within your Atlassian account.

## Use Cases

### The 'Where's the spec?' problem
A dev asks the agent to find the 'Payment Gateway' documentation in Confluence. The agent uses search_content and get_page to pull the requirements into the chat.

### The 'What's my priority?' check
A dev asks for all high_priority frontend bugs in their current sprint. The agent uses search_issues with JQL to list the tickets.

### The 'Sprint Audit' task
A Scrum Master asks the agent to list all active boards and show the current sprint status for each. The agent uses list_boards and list_sprints.

### The 'Release Note' draft
A PM asks the agent to summarize the status of a specific epic. The agent uses get_issue to pull details for all tickets in that epic.

## Benefits

- Stop jumping between tabs by letting your agent pull Jira issue details and Confluence pages into one chat.
- Use search_issues to find high_priority bugs using JQL without having to manually filter through a cluttered dashboard.
- Get a birds_eye view of your team's progress by using list_boards and list_sprints to check active work.
- Access deep documentation instantly with search_content, bringing Confluence specs directly into your project context.
- Keep your team aligned by using list_projects to quickly identify the correct keys for cross_functional tasks.
- Reduce manual status updates by letting your agent audit current sprints and identify blockers automatically.

## How It Works

The bottom line is you get a conversational interface for your Jira and Confluence data.

1. Subscribe to this Connector via the Vinkius marketplace.
2. Enter your Atlassian Domain, Email, and API Token in the setup.
3. Start asking your AI client to find tickets or pull wiki pages.

## Frequently Asked Questions

**Can the Atlassian (Jira & Confluence) MCP help me find specific tickets?**
Yes, it lets your agent search your Jira instance using JQL. You can ask it to find bugs by priority, status, or any other criteria you usually use in the dashboard.

**Does this Connector work for both Jira and Confluence?**
It covers both. You can query your agile boards and issues in Jira while simultaneously pulling text from your Confluence wikis.

**Can my agent read the actual content of my wiki pages?**
Yes, it can retrieve the full rich text content of Confluence pages. This allows your agent to summarize documentation or answer questions based on your internal specs.

**Will this help my team stay updated on our sprints?**
Definitely. You can ask your agent to list active boards and show you the current sprint progress, which helps keep everyone aligned without manual updates.

**Do I need to provide any special keys for the Atlassian (Jira & Confluence) MCP?**
You'll need your Atlassian Domain, Email, and an API Token. Once those are set up in Vinkius, your agent can access your workspace securely.

**Can I use this to search for technical specs during a coding session?**
That's a primary use case. You can ask your agent to find specific architecture docs in Confluence while you're working in your IDE.

**Can my AI write JQL or CQL queries for me automatically?**
Yes. AI models are exceptionally good at transforming natural phrases like 'find all high-priority bugs open in project X' into structurally valid JQL (`project = X AND priority = High AND status = Open`). The same applies to CQL searches in Confluence.

**How does the agent handle Confluence pages with heavy formatting or macros?**
The integration extracts the core text node data of the page. This guarantees that your AI agent only consumes dense factual text (like code snippets and bullet instructions) without wasting token context on layout elements.

**Am I limited to only Jira Software or does this include Jira Service Management?**
The unified underlying Atlassian API allows JQL queries across almost all generic issue types within your authorized Domain instance. You can search bugs in Jira Software or service requests residing structurally alongside them equally.