MCP Server for Jira — User Guide
What is MCP Server for Jira?
MCP Server for Jira gives your AI agents (Rovo, Claude, Cursor) safe, read-only access to your Jira data. Instead of an agent guessing what's in your site, it can search issues with precise JQL, read issue details, request compact issue briefs, check for duplicates, and summarize projects — always with your permissions and without any ability to change data.
Requirements
- Jira Cloud.
- Rovo enabled on your site (organization-verified domain; consumer domains like gmail cannot enable Rovo).
- Installing requires a Jira administrator.
- Using the tools requires nothing beyond a normal Jira account — tools only ever return what you can already see in Jira.
Installation
- Go to Apps → Manage apps (Jira administration).
- Choose Find new apps and search for MCP Server for Jira.
- Click Install and approve the read-only permissions (read work items, read projects, read users).
- The app has no configuration screen — nothing to set up after install.
How to Find the App
The app has no pages, panels, or buttons in Jira itself. It works entirely through Rovo:
- Agent builders: open Rovo Studio → Connected apps — the five tools appear there and can be added to any custom agent.
- Everyone else: once the tools are connected on your site, just ask questions in Rovo Chat — the agent picks the right tool automatically.
The Five Tools
You never call tools by hand — you ask in plain language and the agent chooses. These are the five tools and what they answer:
| Tool | What it does | Example ask in Rovo Chat |
|---|---|---|
Search Jira issues (search-jira-issues) | Runs a precise JQL search, returns a compact list | "Find my open issues in PROJ sorted by updated date" |
Get Jira issue (get-jira-issue) | One issue's full detail: summary, status, description, latest comments | "What's the status of PROJ-123 and what did people comment?" |
Get issue context pack (get-issue-context-pack) | A compact, complete brief of one issue — description, key comments, linked issues — sized for AI reading | "Give me a full brief on PROJ-123 so I can take it over" |
Find similar Jira issues (find-similar-issues) | Duplicate/related check from a sentence or another issue | "Are there existing issues similar to: login fails on Safari 17?" |
Get project overview (get-project-overview) | Project name, description, lead, issue types, most recently updated issues | "Give me an overview of the PROJ project" |
Tips & Common Workflows
- Hand an issue to a teammate fast: ask for a context pack of the issue, then forward the agent's summary — it fits everything important in one short brief.
- Before filing a bug, check for duplicates: describe the bug in one sentence with Find similar Jira issues, optionally narrowed to one project.
- Stand-up prep: combine tools — "Overview of PROJ, then details on the three most recently updated issues."
- Large result sets: if a search comes back marked truncated, narrow it — add a project, a date range, or ask for fewer results.
Troubleshooting
I don't see the tools in Rovo Chat. → Check that Rovo is enabled for your site, and that the tools are connected via Rovo Studio → Connected apps. If your team builds custom agents, make sure the agent includes the five MCP Server for Jira tools.
A search returns issues I know exist, but not all of them — or the response says it's truncated. → The tools return compact result pages on purpose. Narrow the question: add a project, restrict by status or date, or ask for fewer results in your question.
I get empty results, but my teammate sees data. → Tools always run with your permissions. If you can't open the issue in Jira, the agent can't either — ask a project admin for access.
Comments seem to be missing from an issue. → Only the latest comments are included to keep answers compact. Ask specifically: "Show the last 10 comments on PROJ-123."
Can I let the agent edit issues? → No. This app is read-only by design — it cannot create, update, or delete anything.