Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/cfdude/mcp-jiraWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/cfdude/mcp-jira/jira-server)<a href="https://agentmods.dev/mcp/cfdude/mcp-jira/jira-server"><img src="https://agentmods.dev/badge/mcp/cfdude/mcp-jira/jira-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jira-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to jira-server — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "jira-server": { "command": "npx", "args": [ "-y", "jira-server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 9 lines scan A 2885477486c3
jira-server is an MCP server published in the GitHub repository cfdude/mcp-jira (8 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to jira-server, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
jira-mcp-ai
MCP server for Jira Cloud: JQL search, issue reads and gated writes, comments, worklogs, boards and sprints. API-token auth, plan/apply write safety, read-only by default, no telemetry. Runs locally from the jira-mcp-ai npm package. Needs 34 environment variables to run.
jira-admin-mcp
A Model Context Protocol (MCP) server giving AI assistants 78 tools to administer a Jira Cloud site: issues, users, groups, projects, permissions, custom fields, workflows, screens, filters, and bulk operations. Runs locally from the jira-admin-mcp Python package. Needs 4 environment variables to run.
mcp-atlassian-extended
Extended MCP tools for Jira and Confluence — attachments, agile boards, sprints, calendars. Runs locally from the mcp-atlassian-extended Python package. Needs 5 environment variables to run.
atlassian-server-mcp
Unified stdio MCP server for Jira, Confluence, and Bitbucket Data Center. Runs locally from the @zaimokuza/atlassian-server-mcp npm package.
jira-mcp
MCP server exposing the Jira REST API (boards, sprints, issues, JQL, and a generic passthrough) for Jira Cloud and Data Center. Runs locally from the @thammarongg/jira-mcp npm package.
simple-jira-mcp
MCP server "simple-jira-mcp" as configured in timohaa/simple-jira-mcp. Runs locally from the simple-jira-mcp Python package.