Jira MCP server
Yes. Atlassian's Rovo MCP server is the official one for Jira. One hosted endpoint, mcp.atlassian.com/v2/mcp, covers Jira, Jira Service Management, Confluence, Bitbucket and more, signs in with OAuth 2.1, and works inside the permissions your Atlassian account already has. Atlassian documents 52 Jira tools in five permission groups.
https://mcp.atlassian.com/v2/mcpHow to connect it
- Claude Code: run the command below, then run /mcp in a session to sign in.
- Cursor: install the Atlassian server from the Cursor Marketplace.
- VS Code with GitHub Copilot: search @mcp Atlassian in the Extensions view and select Install.
- Claude, ChatGPT and other clients: add https://mcp.atlassian.com/v2/mcp and sign in with your Atlassian account. Gateways that want a flat tool list can append ?tools=all.
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpWhat it can do
- Read work items, comments, changelogs, worklogs, boards, sprints, versions, filters and dashboards (27 read tools)
- Search work items with JQL
- Create and edit work items, change status, comment, log time, link items and manage sprints and versions (15 write tools)
- Reach Confluence, Bitbucket and Atlassian's Projects and Goals through the same connection
What it doesn't do
- Deleting work items, comments or attachments is permanent, so those three tools sit in a delete group that's off by default; an admin has to enable it, and the space-and-workflow admin group too.
- Every MCP call uses Rovo credits from your organization's shared pool, and the cost depends on how much context a call pulls in.
- Its docs don't describe an approval step before an agent's change to a work item counts.
- Existing v1 connections switch to the v2 tools automatically on March 1, 2027; older clients may need their cached credentials cleared.
Staying on Jira?
For a team already on Jira, the Rovo server is the one to use: one sign-in reaches Jira and Confluence, it respects your existing permissions, and admins can switch whole tool groups on or off.
When Done makes sense instead
Done is a to-do app built for handing work to an AI agent, with the parts an agent needs before you trust it with real tasks:
- An approval gate: by default an agent can propose that a task is finished, but only you can close it. Done enforces that, so it holds even if an agent tries to skip it.
- Questions instead of guesses: an agent parks a decision with its recommendation, and you answer in one click.
- Plans before work: an agent can propose a plan that waits for your yes before it starts.
- Lanes: name your agents and pin each task to one, so two agents don't pick up the same work.
- Scoped access: tokens that are read-only or limited to one project or workspace, and budgets an agent can't raise.
Moving takes one step
In Jira, open your project's List (or Filters → Search work items), then ⋯ More actions → Export → Export CSV - all fields. Done reads any CSV with a title column.
Done's import preview shows exactly what lands — projects, tasks, due dates, priorities — before you create an account, and nothing is uploaded.
Preview your Jira importOther to-do apps
Try Done with the agent you already use
Free to start. Connect Claude, ChatGPT or any MCP client in about a minute.
Sources
- support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
- support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/
- support.atlassian.com/jira/kb/how-to-export-issues-from-jira-cloud-in-csv-format
Information about Jira current as of October 2026, checked against the sources above. MCP servers change quickly, so check them before you rely on a detail. Jira is a trademark of its owner.