52
/ 100
1 month ago
glama

Jira MCP Server

Supercharge your AI assistant with seamless Jira integration. Enables AI assistants like GitHub Copilot and Claude to interact with your Jira Cloud instance.

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

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

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: JIRA_OAUTH_CLIENT_ID, JIRA_OAUTH_ACCESS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 12 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: JIRA_API_TOKEN, JIRA_OAUTH_ACCESS_TOKEN, JIRA_OAUTH_CLIENT_SECRET, JIRA_OAUTH_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical12 high12 low

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

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

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

criticalvitest@3.0.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

highaxios@1.13.4GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.13.4GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.13.4GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

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.
configJIRA_ACCEPTANCE_CRITERIA_FIELDCustom field ID for acceptance criteria —
🔐 secretJIRA_API_TOKEN"": "your-api-token"
configJIRA_BASE_URL"": "https://your-domain.atlassian.net",
configJIRA_CLOUD_IDYour Jira Cloud ID ✅
configJIRA_EMAIL"": "your-email@example.com",
🔐 secretJIRA_OAUTH_ACCESS_TOKENAccess token ✅
configJIRA_OAUTH_CLIENT_IDOAuth Client ID ✅
🔐 secretJIRA_OAUTH_CLIENT_SECRETOAuth Client Secret ✅
🔐 secretJIRA_OAUTH_REFRESH_TOKENRefresh 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 6 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/tezaswiraj7222-jira-mcp-mghh8n)](https://m8ven.ai/mcp/tezaswiraj7222-jira-mcp-mghh8n)
commit: 43b32b13f276b92bb9a39cf305971780937d4c6d
code hash: cf2e2eae3770d3ef8210dee7d816a96c78600859f273045df831319131a5b270
verified: 6/22/2026, 12:15:59 PM
view raw JSON →