LabscoMCP early access ↗
rahulthedevilMCP SERVER

Jira Context MCP

Pull a Jira issue, your assigned tickets, or every Bug in a project into the editor and work from there.

by rahulthedevil ↗Project & Task ManagementCommunity

LABSCO SUMMARY

The ticket in the editor, so the fix starts from what was actually written.

This is not about browsing Jira; it is about closing the gap between the ticket and the change. Pull the issue, or every Bug in the project, and the original description sits in the same session as the code, so "fix PROJECT-123" has the requirement in front of it rather than someone's retyped summary. Every documented tool is a read — nothing here moves a ticket or writes a comment.

What it is

A Jira reader for Cursor and other MCP clients. It fetches one issue by key, the issues assigned to you, and issues filtered by type — so the ticket text lands where the code is.

What you get

  • One issue's full detail from its key, so the description and acceptance criteria are in the session
  • The issues assigned to you within a project, capped to a result count you choose
  • Issues filtered to one type — Bug, Story, Epic — across a project
  • Every project the account can reach, and the issue types available in them

Requirements

Node.js 20.17.0 or higher, a Jira account with API access, and an API token generated from Atlassian. Put JIRA_BASE_URL, JIRA_USERNAME and JIRA_API_TOKEN in .env, run npm run build, then start it. It runs as an HTTP server — clients connect to http://localhost:3000/sse by default, and HTTP_PORT moves it — with a CLI mode available as well.

Setup effort

Build from source — git clone https://github.com/rahulthedevil/Jira-Context-MCP.git

See installation options