Jira Issue MCP Server

Enables interaction with Jira through OAuth 2.0 to create and manage issues directly from MCP-compatible clients. It supports secure authentication and local token caching to facilitate automated task management within Jira projects.

→ razvancanuci/jira-issue-mcp-server · listed on glama

Install from

Glama

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

// key findings

🚨

Known vulnerabilities in dependencies: 2 critical, 5 high

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

🔐

You'll be asked for 2 credentials: ATLASSIAN_CLIENT_SECRET, ELASTIC_API_KEY

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

// required environment variables

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

configATLASSIAN_CLIENT_ID— "": "<client id>",

🔐 secretATLASSIAN_CLIENT_SECRET— "":"<client secret>",

🔐 secretELASTIC_API_KEY— "": "<elastic api key>",

configELASTIC_URL— "": "<elastic url>",

configREDIS_HOST— "": "<redis host>",

configSERVER_DOMAIN— "": "<domain>"

// 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 4 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/razvancanuci-jira-issue-mcp-server-l6kjh5)](https://m8ven.ai/mcp/razvancanuci-jira-issue-mcp-server-l6kjh5)

commit: 769f5abd923aa8302bb84cec20f470c187ffe0e1

code hash: 1a54c50afe19eb008737bc838f9899f981bd5bdeab707be63b49d43e69f75e21

verified: 4/11/2026, 2:43:41 PM

view raw JSON →