Atlassian's official remote MCP server connecting Jira Cloud to AI assistants like Claude and Cursor
Provides 25 tools for issue management, JQL search, bulk creation, status transitions, and comments
Zero-setup, OAuth 2.1 secured, enterprise-ready — but limited to Jira Cloud only
Pricing: Free forever
Best for: Individuals & startups
Pros & Cons
Pros
Zero setup — remote server managed by Atlassian eliminates configuration headaches
Full Jira Cloud integration with 25 tools covering issues, projects, comments, and transitions
Enterprise-grade security with OAuth 2.1, permission inheritance, and IP allowlisting
Works with major AI clients including Claude Desktop, Cursor, VS Code, and Zapier
Bulk operations save significant time on repetitive project management tasks
Cons
Limited to Jira Cloud — no support for Jira Server or Data Center editions
Currently in beta with potential feature gaps compared to the full Jira API
Read and write operations depend on Atlassian-hosted infrastructure availability
No custom tool extensibility — limited to Atlassian-defined tool set
Key Features
Real-time Jira issue retrieval, creation, editing, and status transitions via AI assistantsJQL-based issue search directly from Claude, Cursor, or VS CodeBulk operations — create multiple issues or enrich tickets from meeting notes in one promptOAuth 2.1 authentication with full respect for existing Jira permission controlsRemote server hosted by Atlassian on Cloudflare — no local installation requiredComment management and remote issue link access for cross-tool contextProject and issue type metadata retrieval for accurate issue creationIP allowlisting support and encrypted data transmission for enterprise security
Pricing
Free
Jira MCP Server is completely free to use with no hidden costs.
Jira MCP Server is Atlassian's official Model Context Protocol server that connects Jira Cloud to AI assistants like Claude, Cursor, and VS Code. Part of Atlassian's Remote MCP Server infrastructure hosted on Cloudflare, it gives AI tools secure, real-time access to your Jira data without local installation.
The server exposes 25 tools across Jira and Confluence, with Jira-specific capabilities including retrieving issue details, creating and editing issues, transitioning issue statuses, searching with JQL, adding comments, viewing remote issue links, listing projects, and fetching issue type metadata. All actions respect existing Jira permissions through OAuth 2.1 authentication.
Teams use it to summarize work items from natural language prompts, bulk-create issues from meeting notes or specs, enrich tickets by pulling context from multiple sources, and automate repetitive project management tasks. Because it runs as a remote server managed by Atlassian, there is no setup beyond authorizing your Atlassian account. The server supports IP allowlisting and encrypts all data in transit, making it suitable for enterprise environments.
Does Jira MCP Server work with Jira Server or Data Center?
No. The Atlassian Remote MCP Server only supports Jira Cloud. If you run Jira Server or Data Center, you can use the community mcp-atlassian package instead, which connects via personal access tokens and supports both Cloud and on-premises editions.
What AI clients are compatible with Jira MCP Server?
It works with Claude Desktop, Claude Code, Cursor, VS Code (via Copilot agent mode), Windsurf, and Zapier MCP. Any client that supports the Model Context Protocol with HTTP transport can connect using the remote server URL.
Is there a risk of the AI modifying Jira data without permission?
The server enforces existing Jira Cloud permissions through OAuth 2.1. If a user cannot edit an issue in the Jira UI, the AI assistant cannot edit it either. Write operations like issue creation and status transitions require explicit user authorization during the OAuth flow.
How do I set up Jira MCP Server?
No local installation is needed. Add the remote server URL (https://mcp.atlassian.com/v1/sse) to your MCP client configuration, then authorize with your Atlassian account when prompted. The server handles authentication via OAuth 2.1 — no API tokens or manual credential management required.