MCP Atlassian

What is MCP Atlassian?

MCP Atlassian is a Model Context Protocol server that provides comprehensive tools for AI agents to interact with Atlassian products — Confluence and Jira — through a standardized interface. It is designed for developers and teams who want to enable AI-driven automation, search, and content management within their Atlassian environment.

How to use MCP Atlassian?

Install via npm (npm install) or Docker (build and run with Makefile). Create a .env file with your Atlassian host, email, and API token. Start the server using npm start or make start, then configure your MCP client to connect to the streamable HTTP endpoint (e.g., http://localhost:3007/mcp).

Key features of MCP Atlassian

• Uses Confluence v2 REST API with v1 fallback for search
• Provides 18+ Confluence tools and 8+ Jira tools
• Built-in PII filtering and SSL verification controls
• Supports flexible authentication and tool filtering
• Cursor-based pagination for v2 APIs; offset/limit for v1
• Comprehensive error handling with detailed messages
• Full TypeScript implementation with type safety

Use cases of MCP Atlassian

• Automate Confluence page creation, updates, and labeling
• Search Confluence content and spaces using CQL or title
• Manage Jira issues: create, update, search, and transition
• Retrieve project lists and issue details for reporting
• Add comments and manage workflows across both products

FAQ from MCP Atlassian

What are the prerequisites for using MCP Atlassian?

You need Node.js v16 or higher, npm or yarn, an Atlassian account with an API token, and optionally Docker for containerized deployment.

How do I authenticate with the Atlassian APIs?

Provide your Atlassian host, email, and API token in a .env file (ATLASSIAN_HOST, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN). The server supports basic auth, with OAuth 2.0 and PAT tokens planned.

Can I restrict the server to read-only operations?

Yes. Set READ_ONLY_MODE to disable all write operations for safe exploration. You can also use tool whitelisting via the ENABLED_TOOLS environment variable.

Which Confluence API versions are used?

The server primarily uses the Confluence v2 REST API for spaces, pages, comments, and labels. It falls back to the v1 API for content search (CQL) because v1 offers more powerful search capabilities.

Does the server support self-hosted Atlassian instances with custom SSL?

Yes. SSL verification bypass is configurable, allowing you to connect to self-hosted or on-premises instances with custom certificates.