Atlassian MCP Server (Jira + Confluence)

Popular MCP server integrating both Jira and Confluence — enabling AI agents to create and query Jira issues, manage sprints, read and write Confluence pages, search across both platforms, and automate Atlassian-powered development workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent

Homepage ↗ Repo ↗ Developer Tools atlassian jira confluence mcp-server project-management documentation agile

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

100

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

HTTPS enforced. User-scoped API tokens. OAuth2. FedRAMP, SOC 2, ISO 27001, GDPR, HIPAA. Enterprise SSO.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

An agent needs to interact with Jira issues or Confluence pages — especially in enterprise development teams using Atlassian's toolchain.

Avoid When

You're using Linear, GitHub Issues, or another issue tracker.

Use Cases

• Creating and updating Jira issues from development workflow agents
• Querying sprint progress and backlog from project management agents
• Reading Confluence documentation for context-aware coding agents
• Searching Jira and Confluence for relevant information from research agents
• Triaging bugs and creating tickets from monitoring/alerting agents
• Updating project documentation from DevOps pipeline agents

Not For

• Teams using Linear, Asana, or other issue trackers
• Teams without Atlassian Cloud or Data Center licenses
• Real-time collaboration (Atlassian is async-first)

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Yes

OpenAPI Spec ↗

Authentication

Methods: api_token basic_auth oauth2

OAuth: Yes Scopes: Yes

Atlassian API tokens (user-level) for Cloud. OAuth2 for apps. Basic auth for Data Center. Jira and Confluence use separate tokens.

Pricing

Model: per-seat

Free tier: Yes

Requires CC: No

Atlassian Cloud pricing per user. Data Center is perpetual license. MCP server is community open source.

Agent Metadata

Pagination

cursor

Idempotent

Partial

Retry Guidance

Not documented

Known Gotchas

⚠ Jira Cloud vs Data Center have different API paths and auth mechanisms
⚠ JQL (Jira Query Language) knowledge required for effective issue queries
⚠ Confluence page IDs and space keys required for page operations
⚠ Custom fields in Jira have UUID field IDs — discovery required
⚠ Rate limits can be hit during bulk operations — agents must throttle
⚠ API tokens are user-scoped — impersonation not possible without OAuth apps

Alternatives

mcp-server-asana linear-mcp monday-com

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Atlassian MCP Server (Jira + Confluence).

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.