Jira MCP server: setup, auth, production
Last verified: June 2026· Jira MCP integration
Community MCP servers existIssue and project tracking across large organizations.
What is the Jira MCP server?
A Jira MCP server implements the Model Context Protocol and exposes Jira's capabilities as typed tools an agent can discover and call in the middle of a task. Issue and project tracking across large organizations.
Connecting the tracker closes the loop between a code change and the work item behind it: the agent reads the spec it is implementing and updates status without a human relaying it. OAuth per user and team scoping keep it honest.
A real Jira workflow
The agent transitions a ticket through its workflow as the code moves — reading the requirement, linking the PR, and generating the release-note line from the closed issues — across projects that would otherwise need manual bookkeeping.
What an agent can do with Jira
- Have an agent open, update, and transition tickets
- Pull requirements and linked tickets for context
- Generate a release-notes summary from closed issues
Read-only is the right default: let the agent observe and reason first, then grant specific write actions deliberately — each behind audit logging and, for anything high-impact, human approval.
Setting up the Jira MCP server
Use an Atlassian OAuth app or an API token scoped per project. Jira’s workflow transitions are permission-gated; grant only the transitions the agent should be able to make.
Auth: Atlassian OAuth or API token with project-scoped permissions. Credentials belong in the environment or a secret store — never in the repo or the agent's sandbox. Wiring a server into Claude Code or Cursor is the same for every tool; the step-by-step lives in the MCP connection guide.
The risk to watch with Jira
Jira state transitions can trigger automations and notifications downstream. Scope the transitions the agent can perform, or a status change becomes a cascade of unintended side effects.
More broadly, a production-grade Jira integration needs permission scoping across projects and safe state transitions. The MCP security checklist applies to every integration — we build servers with these controls baked in.
Troubleshooting
If the Jira tools don't appear after setup, it's almost always auth or transport. See MCP server not connecting for the step-by-step fix — and note that hosted servers often need OAuth, not a plain API key. To understand how MCP relates to ordinary tool use, see MCP vs function calling.
Frequently asked questions
Is there an official MCP server for Jira?
Community MCP servers exist. Whichever you use, a production setup needs permission scoping across projects and safe state transitions.
How does authentication work for Jira over MCP?
Atlassian OAuth or API token with project-scoped permissions. Credentials should never live in the sandbox or the repo; route them through your client's secret handling or a vaulted credential.
What can an agent actually do with Jira?
Have an agent open, update, and transition tickets; Pull requirements and linked tickets for context; Generate a release-notes summary from closed issues. Start read-only and add write access deliberately, behind audit logging.
Is it safe to give agents access to Jira?
Yes, when scoped correctly: least-privilege credentials, read-only by default, audit logs on every call, and human approval for any high-impact action. Permission scoping across projects and safe state transitions.