# Jira & Confluence — MCP Server

> Search Jira and Confluence, move tickets, and keep docs aligned with in-flight work.

**Source:** https://mcpplaygroundonline.com/mcp-servers/jira  
**Transport:** sse  
**Requires auth:** Yes

---

## What it does

The Jira and Confluence MCP is aimed at product and engineering orgs: search and read Confluence runbooks while updating Jira epics, create sub-tasks from a meeting note, and cross-link documentation to active bugs. The server’s tools reflect what your Atlassian Cloud user can do with your existing permissions, so a contributor cannot magically bypass project roles. In MCP Playground, use the Jira and Confluence template: it keeps the right URL and token hints in sync with Atlassian’s documentation.

## Tools exposed

- Search and read Jira issues, epics, and boards; update status, assignee, and fields where allowed
- Search, read, and (with scopes) create or update Confluence pages and inline comments
- Map work items to documentation: find the Confluence spec linked to a Jira key

## Example queries you can run

- "List all In Progress items assigned to me in the Platform board with blockers called out."
- "Create a Jira task under the Mobile epic titled “Fix crash on cold start for iOS 18”."
- "Find the Confluence page that describes our release train and pull the key dates."

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — Claude Sonnet 4.5 is best for long Confluence context plus Jira state changes. For quick JQL lookups, Haiku 4.5 is enough; test both in Agent Studio.
- **Transport:** sse
- **Authentication:** Required — Atlassian API token from id.atlassian.com (Security → API tokens) and your Atlassian account email. Some clients send `user:token` for basic auth; follow the template’s field guidance.
- **Hosted endpoint:** https://mcp.atlassian.com/v1/sse
- **Official source:** [Atlassian developer documentation](https://developer.atlassian.com)

## Frequently asked questions

### What is the Jira and Confluence MCP server?

It is Atlassian’s remote MCP service for cloud products that exposes Jira work items, boards, and Confluence pages to AI tools through a standard tool surface, using your existing Atlassian account permissions rather than a separate shadow integration.

### What credentials do I use for the Atlassian MCP server?

Create a personal Atlassian API token in your Atlassian account, keep your work email, and add both to the MCP client according to the server’s expected scheme — often a paired email and token for HTTP basic auth, or a bearer form your client documents.

### Can the model edit any Jira project I can see?

The model is limited to what your Jira and Confluence roles allow. A reader cannot close epics, and a Jira Software user cannot see pages in a restricted Confluence space. If you are testing write behaviour, do it in a test project with disposable issues.

### Does the Atlassian MCP server work with Jira Data Center on premise?

The hosted mcp.atlassian.com endpoint is built for Atlassian Cloud. On-prem and Federation setups may require different network paths; consult your admin before routing production traffic through a third-party MCP client.

### Which model should I use for Jira plus Confluence workflows?

Claude Sonnet 4.5 is a good default when you are jumping between a long spec page, comments, and several Jira issues, because the model can hold cross-links in context. You can A/B a cheaper model in Agent Studio for pure JQL one-liners.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/jira — free, no install._