Jira Cloud

io.github.aaronsbPublished by GitHub account aaronsbv0.11.3Updated Oct 25, 2026

MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper ToolsData & Analytics

Overview

AI-generated overview

A local MCP server that lets an assistant read and change Jira Cloud issues, sprints, boards, filters and projects through your Atlassian account.

What you can do
Get, create, update, delete, move, transition, comment on and link issues, and traverse issue hierarchies. Search with JQL and manage saved filters. List projects and boards, and read their configuration and metadata. Create, start and close sprints and assign issues to them. Batch several operations with result references and error strategies, and compute metrics or counts over JQL-selected issues. Read instance, project, board and custom-field overviews as resources.
When to use it
Useful when you want an assistant to work inside an existing Jira Cloud setup: triaging and updating tickets, running JQL searches, planning sprints, or producing metrics and reports from issue data without switching tools.
Requirements
Runs locally via npx, so Node.js is needed. Requires a Jira Cloud instance URL in JIRA_HOST, an Atlassian account email in JIRA_EMAIL, and an API token in JIRA_API_TOKEN generated from Atlassian account settings. Network access to your Jira instance.
Before you install
The API token is a credential granting access to your Jira account; keep it out of shared configuration. Tools can create, update, delete, move and transition issues and change sprints, so assistant actions modify real project data. Issue content and project metadata are sent to the Jira instance you configure.

Installation

In SourceWeft

  1. Open Jira Cloud in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Jira Cloud MCP Server

A Model Context Protocol server for interacting with Jira Cloud instances.

Install

Claude Desktop (one-click)

Download jira-cloud-mcp.mcpb and open it — Claude Desktop will prompt for your Jira credentials.

Claude Code

bash
claude mcp add jira-cloud -e JIRA_API_TOKEN=your-token -e JIRA_EMAIL=your-email -e JIRA_HOST=https://your-team.atlassian.net -- npx -y @aaronsb/jira-cloud-mcp

Manual (any MCP client)

json
{  "mcpServers": {    "jira-cloud": {      "command": "npx",      "args": ["-y", "@aaronsb/jira-cloud-mcp"],      "env": {        "JIRA_API_TOKEN": "your-api-token",        "JIRA_EMAIL": "your-email",        "JIRA_HOST": "https://your-team.atlassian.net"      }    }  }}

Credentials

Generate an API token at Atlassian Account Settings.

Tools

ToolDescription
manage_jira_issueGet, create, update, delete, move, transition, comment on, link, or traverse hierarchy of issues
manage_jira_filterSearch for issues using JQL queries, or manage saved filters
manage_jira_projectList projects or get project configuration and metadata
manage_jira_boardList boards or get board details and configuration
manage_jira_sprintManage sprints: create, start, close, and assign issues to sprints
queue_jira_operationsBatch multiple operations with result references ($0.key) and error strategies
analyze_jira_issuesCompute metrics, exact counts, and data cube analysis over issues selected by JQL

Each tool accepts an operation parameter (except queue_jira_operations which takes an operations array, and analyze_jira_issues which takes jql + metrics). Per-tool documentation is available as MCP resources at jira://tools/{tool_name}/documentation.

See docs/tools.md for detailed tool descriptions, workspace patterns, and design principles.

MCP Resources

ResourceDescription
jira://instance/summaryInstance-level statistics
jira://projects/distributionProject distribution overview
jira://projects/{key}/overviewProject overview with status counts
jira://boards/{id}/overviewBoard overview with sprint info
jira://issue-link-typesAvailable issue link types
jira://custom-fieldsCustom field catalog (auto-discovered at startup)
jira://custom-fields/{project}/{issueType}Context-specific custom fields
jira://analysis/recipesAnalysis query patterns and compute DSL reference
jira://tools/{name}/documentationPer-tool documentation

License

MIT License

Source: README.md at commit 71073e0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.11.3LatestSep 23, 2026
  2. v0.11.2Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.