Mcp Jira Server

io.github.edrich13Published by GitHub account edrich13v1.0.1Updated Oct 25, 2026

MCP server for self-hosted Jira instance with Personal Access Token authentication

VerifiedSTDIODesktop onlyProductivity & Workflow Developer Tools

Server details

Identifier: io.github.edrich13/mcp-jira-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account edrich13 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.edrich13%2Fmcp-jira-server.svg)](https://sourceweft.com/mcp/io.github.edrich13%2Fmcp-jira-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that connects an AI assistant to a self-hosted Jira instance using Personal Access Token authentication.

What you can do: Connects an assistant to a self-hosted Jira instance over its base URL and a Personal Access Token, so Jira work can be handled from the assistant. The manifest lists no tools, so the exact operations are not documented here; expect typical Jira actions such as reading and working with issues, depending on what the package exposes.
When to use it: Worth adding when you run your own Jira instance and want an assistant to work with it directly, rather than through a hosted Jira cloud integration.
Requirements: Runs as a local process on the user's machine, installed from the npm package mcp-jira-server, so Node.js is needed. Requires the JIRA_BASE_URL environment variable with the base URL of your Jira instance and the JIRA_PAT environment variable holding a Personal Access Token. Network access to that Jira instance is required.

Before you install

The server needs a Jira Personal Access Token, passed in the JIRA_PAT environment variable; treat it as a sensitive credential and keep it out of shared configuration. The manifest lists no tools, so what the assistant can read or change in Jira is not documented here; check before pointing it at a production instance.

Installation

In SourceWeft

Open Mcp Jira Server in the dashboard and add it to a workspace.
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.

Tools

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

Version history

v1.0.1LatestSep 16, 2026

Score

25% 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
Declare a license in the repository or the registry entry.