Claude Desktop Jira MCP: Connect and Review Tasks
You can connect Claude Desktop to Jira through an MCP server, letting Claude read and review Jira issues in a conversation. This guide covers how the connection works, what to check about access and permissions, and how fenbs keeps cross-session decisions and handoff notes linked to the source work.
Updated 5 min read
Claude Desktop supports MCP (Model Context Protocol), which lets you connect it to external tools including Jira. With a Jira MCP server configured, Claude can read issue details, list tasks in a project, check status, and help you analyze what is in the board — all within a conversation. This is a desktop-specific connection: it uses the MCP configuration in Claude Desktop, not a separate integration in Claude.ai.
For decisions and notes that need to travel with the work across sessions and tools, fenbs keeps a separate record any connected AI can read. When Claude picks up a Jira review task in a later session, the decisions from the last session are still there.
How Claude Desktop MCP connections work
Claude Desktop reads MCP server configuration from a JSON file on your computer. You add an entry for each server you want Claude to connect to, specifying how to start the server process and any environment variables it needs (such as an API token). When Claude starts, it launches those servers and lists their available tools.
The config file location varies by operating system. On macOS it is at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it is at %APPDATA%\Claude\claude_desktop_config.json. Anthropic's own documentation has the current path and format — check it if you have a newer version of Claude Desktop, as the path can change.
If your configuration is not loading correctly, the Claude Desktop MCP not working guide covers the most common causes. The Claude Desktop MCP config guide has the full configuration reference.
Finding or building a Jira MCP server
Atlassian does not publish an official Jira MCP server. Several community-built servers exist on GitHub and in MCP directories. Before installing one, check:
- Is it using the official Jira REST API? The public API is stable; unofficial approaches may break.
- What credentials does it need? A Jira API token tied to your account is the expected pattern. Never give a server your Jira password directly.
- What can it actually do? Read issues, write comments, transition status? Confirm that the actions it advertises are the ones you need.
- When was it last updated? The MCP spec has evolved and older servers may use deprecated patterns.
The what can Jira MCP do guide explains the range of actions a well-built server can expose. The Jira MCP with Claude Code guide covers the Claude Code variant of the same connection, which differs in configuration.
Checking access and permissions
The Jira MCP server acts on behalf of the Jira user whose API token you provide. That user's Jira permissions govern what the server can read or change. If that user cannot see a project in Jira, the server cannot read it through MCP either.
After connecting, verify what Claude can actually see by asking it to list the projects your token has access to. Compare that list to what you expect. If projects or issues are missing, check the token permissions in Jira's account settings first.
Be deliberate about which Jira user's token you use. A token with write access allows Claude to add comments, change status, and update fields. If you only need read access for now, create a token with minimal permissions and upgrade when you need more.
Keep decisions and handoff notes linked to the source work
When Claude reviews Jira issues, the observations and decisions that follow — which issues need attention, what was agreed, what the next steps are — live in that conversation and can easily get lost. Save them in fenbs: decisions in Decisions and rules, tasks on the board, sources in Links and listings. Any session that connects to fenbs reads the same record. Free to start.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
Testing the connection
Once the Jira MCP server is running and listed in Claude Desktop, test it with a simple, known question: ask Claude to list the Jira projects the connection can see and compare the result to what you expect. Then ask about a specific issue you know the details of and check whether the summary is accurate. This confirms both that the connection works and that the token has the right access before you use it for real work.
What the connection can and cannot do
A Claude Desktop Jira MCP connection lets Claude read the Jira issues you ask about, summarize them, suggest priorities, and answer questions about the board. It can make changes in Jira — comments, status transitions, field updates — if the server supports those actions and the token has write access.
It does not give Claude memory of previous Jira conversations. Each new Claude Desktop session starts fresh. Decisions from last week's review, the rule about which issues get escalated first, the note about a team member's upcoming absence — none of that carries over unless it is somewhere Claude can read at the start of the session.
How to do this with fenbs
- Create a free account and add a project corresponding to the Jira work you are reviewing.
- Connect Claude Desktop to the Jira MCP server by editing the Claude Desktop config file with the server details.
- Connect Claude Desktop to fenbs from Integrations so Claude can read both Jira and the shared work record.
- Write the rules for Jira review — what gets escalated, what can be closed without review — in Decisions and rules in fenbs.
- At the start of each Jira review session, ask Claude to read the fenbs project context. After the session, save the key decisions and next steps back to fenbs for the next session.