Atlas / MCP servers / rahulthedevil / Jira Context

Jira ContextSAFE

mcp/rahulthedevil/jira-context

MCP server to provide Jira Tickets information to AI coding agents like Cursor

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
5 5r · 0w · 0d
Transport
sse · stdio
License
MIT
Stars
26
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://mseep.ai/app/rahulthedevil-jira-context-mcp)

[](https://github.com/rahulthedevil/Jira-Context-MCP/actions/workflows/codeql.yml) [](https://smithery.ai/server/@rahulthedevil/Jira-Context-MCP) [](https://mseep.ai/app/d3bb0c74-58fd-4683-a3c7-99cc0342eecc)

A Model Context Protocol (MCP) implementation for Jira that allows you to:

  • Input a Jira ticket link to fetch issue details and instruct Cursor to fix it
  • Retrieve all tickets assigned to you within a specified Jira project
  • Filter Jira issues based on a specific issue type and automatically direct Cursor to resolve them
  • Integrate seamlessly with Jira's API for automation and efficiency

Setup

Prerequisites

  • Node.js 20.17.0 or higher
  • A Jira account with API access
  • A Jira API token (can be generated at Atlassian API Tokens)

Installation

Installing via Smithery

To install Jira Context MCP for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @rahulthedevil/Jira-Context-MCP --client claude

Installing manually

  1. Clone this repository:
git clone https://github.com/yourusername/Jira-Context-MCP.git
cd Jira-Context-MCP
  1. Install dependencies:
npm install
# or if you use pnpm
pnpm install
  1. Create a .env file based on the example:
cp
Read from source at commit e2aa08a80983OBSERVED · 2026-10-09
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add jira-mcp --env JIRA_API_TOKEN=${JIRA_API_TOKEN} -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "jira-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}"
      }
    }
  }
}
03

Exposed tools (5)

5 read · 0 write · 0 destructive.

ToolRiskDescription
get_assigned_issuesreadGet issues assigned to the current user in a project
get_issuereadGet detailed information about a Jira issue
get_issue_typesreadGet list of available Jira issue types
get_issues_by_typereadGet issues of a specific type
get_projectsreadGet list of available Jira projects
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (2 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (2)

LOWInventory / provenance · inv.hidden_file · CWE-1104
.eslintrc.js
.eslintrc.js
Why it matters. hidden member outside the usual dotfiles
Fix. review its purpose
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk, axios, cross-env, dotenv, express, remeda, zod, @types/express
Why it matters. 19 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-09 · audit v0.4.1 · source sha e2aa08a80983full audit observations/trust-audit/mcp-server/rahulthedevil__jira-context.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-09e2aa08a80983SAFEB89first audit
06

Questions

What is the Jira Context MCP server?

MCP server to provide Jira Tickets information to AI coding agents like Cursor

What tools does Jira Context expose?

5 in total: 5 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Jira Context safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Jira Context need?

It reads JIRA_API_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does Jira Context run?

It speaks sse and stdio, so it runs as a local process your client starts. It is published on npm as jira-mcp at 0.1.0.

How current is this page?

The grade is for one exact copy of the source (e2aa08a80983), read on 2026-10-09. The repository is watched and re-audited when it changes.

Advertisement