How to Set Up the Jira MCP Server (and What It Cannot See)
A straight setup guide for Atlassian’s own MCP server: one command, one login, done. Then the part nobody tells you, which is where its reach stops and what to add when your questions turn to testing.
Connecting the agent is easy. Knowing what it can answer is not.
Atlassian’s MCP server is genuinely good and takes about two minutes to set up. Your agent can then search Jira, read work items, create and update them, and pull Confluence pages, all with your own permissions. If that is what you came for, the next section is all you need and you can stop there.
The surprise comes later, usually the first time someone asks a testing question. "Which stories in this sprint are untested?" comes back thin or empty, and it looks like the agent failed. It did not. It answered honestly about everything it could see, and your test cases were not in that set.
Connect your agent to Jira
Atlassian hosts the server, so there is nothing to install or run locally. This takes about two minutes and covers Jira, Jira Service Management, Confluence, and Bitbucket.
Add the server to your agent
Atlassian’s hosted endpoint is the same for everyone. In Claude Code, register it with one command:
Claude Code · terminalclaude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2Atlassian renamed this server once already, from Remote MCP Server to Rovo MCP Server. If the endpoint does not resolve, check their current documentation before assuming your setup is wrong.
Authenticate
Start a session and run the MCP command. Your browser opens an Atlassian consent screen; approve it and the connection is live.
Claude Code · inside a session/mcpAuthentication is OAuth 2.1. The agent then acts as you, with exactly your existing permissions, and every action is attributable to your account.
Confirm it works
Ask the agent something only Jira can answer. If it returns real work items, you are connected.
try thisList the open work items assigned to me in Jira.Notice what it cannot answer
Now ask a testing question. If your test cases live outside Jira issues, the agent answers thin or empty, and it is not a setup error. That gap is the subject of the rest of this page.
try this tooWhich of my sprint stories have no test coverage?
Other clients
- Cursor
- Install from the Cursor marketplace, or add the same endpoint as an HTTP MCP server in settings.
- VS Code
- Search Extensions for the Atlassian MCP entry, or use Atlassian’s one-click install link.
- Anything else
- Any MCP-compatible client works. Point it at the same endpoint over HTTP transport and authenticate with OAuth.
Atlassian owns these instructions and has changed them before. If anything here does not match, trust Atlassian’s own getting-started guide over this page.
The Atlassian MCP handles Jira.
The BesTest MCP handles testing.
Every vendor brings their own MCP to the party. You add both to your agent once, then watch what one sentence sets in motion.
What is our coverage on the checkout requirements, and which gap is riskiest?
+ more
Atlassian ships thisAtlassian MCPOfficially the Rovo MCP Server. Most people say "the Jira MCP".
idle - no Jira call needed here
We ship thisBesTest MCPClosed beta, access granted per user. GA soon.
What lands
Coverage at 71%, with the riskiest gap named rather than just the lowest one.
Riskiest is not simply lowest: significance weights complexity times impact.
Plan in Jira. Test in BesTest. One conversation.
Illustrative conversation · the BesTest MCP is in closed beta
How it fits Rovo
Through your agent, BesTest pairs with Atlassian’s Teamwork Graph: their MCP brings the org-wide context, ours brings the testing depth.
With the Jira MCP alone
- Reads work items, sprints, epics, comments, and Confluence pages
- Creates and updates issues from a sentence
- Cannot see test cases, cycles, executions, or coverage
- Answers "what are we building?" but not "is it tested?"
With both MCPs connected
- One agent, one conversation, spanning planning and testing
- Coverage answered per sprint, epic, or release, not per tool
- A bug can be traced to its requirement and to the tests that should have caught it
- Acceptance criteria in Jira become linked test cases in BesTest
One prompt, start to finish
Which stories in the current sprint have no test coverage yet, and which one is riskiest to ship?- 1
Asks Jira what is in the sprint
Through Atlassian’s MCP the agent pulls the active sprint and its work items, with status, assignee, and acceptance criteria. This half is the part the Jira MCP does well.
- 2
Asks BesTest what is covered
Through the BesTest MCP it pulls requirements and test cases linked to those same work items, plus coverage, which is significance-weighted rather than a simple has-a-test flag.
- 3
Joins the two and ranks the risk
It matches them on the work item link both sides already share, then sorts the gaps by significance. Neither MCP could have answered this alone; the answer only exists in the join.
The result
This is the point of running both. The Jira MCP knows what you are building. The BesTest MCP knows whether it is tested. Connected together, your agent answers the question a release actually turns on, and it answers it in one sentence rather than two tools and a spreadsheet.
The story list comes from Atlassian’s MCP, the coverage from the BesTest MCP. The join happens on the work item link the two already share.
More prompts to steal
A bug just landed on JIRA-509. Which requirement does it break, and which tests should I re-run?
Turn the acceptance criteria on JIRA-412 into test cases and link them back to the story.
Is release 4.2 ready? Show me what is in it from Jira and its coverage and last results from BesTest.
Summarize testing status for the payments epic for tomorrow’s standup.
Scoped to your permissions, granted per user
Your agent acts as you: everything it reads or writes stays inside your Jira permissions. The MCP is in closed beta while we harden it, with GA coming. The request form asks for a few details from BesTest’s Project Settings in your Jira, which is what lets us enable exactly your site and user.
Request beta accessFrequently asked questions
What is the Jira MCP server URL?
Atlassian’s hosted endpoint is https://mcp.atlassian.com/v1/mcp/authv2. It is a remote server, so nothing runs on your machine. In Claude Code the command is: claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2, then /mcp in a session to authenticate. Cursor and VS Code offer one-click installs. Atlassian has renamed this server once already, from Remote MCP Server to Rovo MCP Server, so check their getting-started doc if the endpoint does not resolve.
Can the Jira MCP server see my test cases?
Only if your test cases are stored as Jira issues. Tools like Xray and Zephyr Scale do exactly that, so Atlassian’s MCP can see them, at the cost of every test and every execution living in your issue tracker. BesTest deliberately keeps test cases out of Jira issues, so a 300-run cycle adds nothing to your backlog. The trade-off is that Atlassian’s MCP cannot see them, which is precisely why BesTest ships its own MCP server.
Do I have to choose between the Jira MCP and the BesTest MCP?
No, and choosing would defeat the point. MCP is designed for an agent to hold several connections at once. Every vendor publishes its own; you add each one you want. Running Atlassian’s alongside the BesTest MCP is the intended setup, and the questions worth asking, like sprint coverage or release readiness, are the ones that need both.
Is it safe to give an agent access to Jira?
Authentication uses OAuth 2.1, so the agent operates with your existing permissions and nothing more. It cannot reach a project you cannot reach, and its actions are attributable to your account. The BesTest MCP follows the same principle: scoped access, your permissions, and a record of what was done. Treat agent access like any other account access, and grant it to people you would already trust with the data.
Does this need a paid Atlassian plan?
Atlassian gates availability by product and plan and has changed the terms more than once, so check their current getting-started documentation rather than trusting a third-party page, including this one. The BesTest MCP is in closed beta: it is available on request to BesTest users while we harden it, including teams on the free tier, with general availability to follow.
Ready to Get Complete
Testing Visibility?
Start using BesTest today and experience complete testing visibility from requirements to release. Free to get started!
Available on the Atlassian Marketplace. Install in seconds, free for up to 10 users.
Start Free on Marketplace