Atlassian Jira

io.github.magurelabsPublished by GitHub account magurelabsv2.0.0Updated Nov 14, 2026

Search, create and transition Jira issues, worklogs, links and attachments.

The publisher's own server: Atlassian Rovo MCP Server

Overview

AI-generated overview

Connects an assistant to Jira so it can search, create and transition issues, and manage worklogs, links and attachments.

What you can do
  • Search Jira issues
  • Create issues and move them through workflow transitions
  • Add worklogs, link issues and manage attachments
When to use it
Useful when you want an assistant to look up Jira tickets, file new issues, update their status, or log time and attach material without switching to the Jira web UI.
Requirements
Runs as a local Docker image (streamable-http transport) on a desktop machine. Needs the MCP_MODE setting, which defaults to platform mode; hosted and local modes require additional configuration. Platform mode requires the MCP_SERVICE_TOKEN secret, sent by callers as the X-Service-Token header.
Before you install
The server creates and changes Jira data (issues, transitions, worklogs, links, attachments), so mistakes affect shared team trackers. It requires a shared service token (MCP_SERVICE_TOKEN) that callers present as X-Service-Token; keep it secret. Authentication to Jira itself is not described in the supplied material, so confirm how Jira credentials are supplied before use.

Installation

In SourceWeft

  1. Open Atlassian Jira 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

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v2.0.0LatestNov 14, 2026

Score

35% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Atlassian integrations