jira-dev-mcp

Item: jira-dev-mcp
Rating: 74
Author: M8ven

A local MCP server for Jira Cloud-driven development. Connects MCP clients to Jira for searching issues, reading tasks, parsing attachments, and mapping projects to local repos.

→ nianyi778/jira-dev-mcp · listed on glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings

🚨

Secret credentials may flow to a network call

1 flow detected: JIRA_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.

🚨

Known vulnerabilities in dependencies: 1 critical, 1 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

🔐

You'll be asked for 3 credentials: JIRA_API_TOKEN, JIRA_CLIENT_SECRET, JIRA_TOKEN

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// known CVEs in dependencies1 critical1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@4.0.18GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// required environment variables

This server reads these from process.env. You'll be asked to provide them before it can run.

🔐 secretJIRA_API_TOKEN

configJIRA_AUTH_MODE

configJIRA_BASE_URL— export ="https://your-domain.atlassian.net"

configJIRA_CLIENT_ID— Advanced: To use your own OAuth app, set and JIRA_CLIENT_SECRET before running jira-dev login.

configJIRA_CLIENT_ID_BUILTIN

🔐 secretJIRA_CLIENT_SECRET— Advanced: To use your own OAuth app, set JIRA_CLIENT_ID and before running jira-dev login.

configJIRA_CLIENT_SECRET_BUILTIN

configJIRA_EMAIL— export ="you@example.com"

🔐 secretJIRA_TOKEN— export ="your-jira-api-token"

// full audit trail

The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.

// improvement guidance — verified publishers only

We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/nianyi778-jira-dev-mcp-1a4hby)](https://m8ven.ai/mcp/nianyi778-jira-dev-mcp-1a4hby)

commit: f8a9c8b1d9b0a04f016180cb6f86051584b7fb83

code hash: 4a393caa8cd8752b33e6b4d22915c50e65ece4d52487acc18b0e66fae33a953d

verified: 7/21/2026, 9:05:16 AM

view raw JSON →