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/IvanBBaev/jira-mcpWrote 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/ivanbbaev/jira-mcp/jira-mcp-ai)<a href="https://agentmods.dev/mcp/ivanbbaev/jira-mcp/jira-mcp-ai"><img src="https://agentmods.dev/badge/mcp/ivanbbaev/jira-mcp/jira-mcp-ai/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ivanbbaev/jira-mcp/jira-mcp-ai"><img src="https://agentmods.dev/badge/mcp/ivanbbaev/jira-mcp/jira-mcp-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jira-mcp-ai 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 9d 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.
What it actually says
{
"jira-mcp-ai": {
"command": "npx",
"args": [
"-y",
"jira-mcp-ai"
],
"env": {
"JIRA_SITE": "",
"JIRA_EMAIL": "",
"JIRA_API_TOKEN": "",
"JIRA_ENV_FILE": "",
"JIRA_TOKEN_EXPIRES": "",
"JIRA_ALLOWED_HOSTS": "",
"JIRA_ACTIVE_PROFILE": "",
"JIRA_LOCK_PROFILE": "true",
"JIRA_TOOL_PACKAGES": "all",
"JIRA_PACKAGES_DENY": "",
"JIRA_PACKAGES_READONLY": "",
"JIRA_WRITE_MODE": "plan",
"JIRA_ALLOW_IRREVERSIBLE": "false",
"JIRA_REQUEST_TIMEOUT_MS": "30000",
"JIRA_CALL_BUDGET_MS": "120000",
"JIRA_HOST_CONCURRENCY": "4",
"JIRA_RETRY_ATTEMPTS": "3",
"JIRA_MAX_RESULT_CHARS": "25000",
"JIRA_MAX_PAGES": "20",
"JIRA_MEDIA_DIR": "",
"JIRA_TRANSPORT": "stdio",
"JIRA_HTTP_PORT": "3334",
"JIRA_HTTP_TOKEN": "",
"JIRA_LOG_LEVEL": "info",
"JIRA_JOURNAL_PATH": "",
"JIRA_AUTH_MODE": "basic",
"JIRA_OAUTH_CLIENT_ID": "",
"JIRA_OAUTH_CLIENT_SECRET": "",
"JIRA_OAUTH_SCOPES": "read:jira-work,write:jira-work,read:jira-user,manage:jira-project,read:board-scope:jira-software,write:board-scope:jira-software,read:sprint:jira-software,write:sprint:jira-software,read:epic:jira-software,write:epic:jira-software,read:issue:jira-software,write:issue:jira-software,offline_access",
"JIRA_OAUTH_CLOUD_ID": "",
"JIRA_OAUTH_TOKEN_FILE": "<config dir>/oauth.json",
"JIRA_OAUTH_REDIRECT_PORT": "8250",
"JIRA_OAUTH_AUTH_ORIGIN": "https://auth.atlassian.com",
"JIRA_OAUTH_GATEWAY_ORIGIN": "https://api.atlassian.com"
}
}
}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.
- 9d ago First seen · 45 lines scan A abfb1aaafe94
jira-mcp-ai is an MCP server published in the GitHub repository IvanBBaev/jira-mcp (0 stars, last pushed 4d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
atlassian-mcp-server
MCP server for Atlassian APIs (Jira, Confluence, Bitbucket). Runs locally from the @jagadeesh52423/atlassian-mcp-server npm package.
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.
atlassian-mcp
MCP server for Jira & Confluence — 53 tools for issue management, sprint planning, board management, and Confluence page management. Runs locally from the atlassian-mcp Python package.
jira-server
Enterprise-grade Model Context Protocol server for comprehensive Jira integration with automated field detection, multi-instance support, and cross-server capabilities. Runs locally from the jira-server npm package.
jira-mcp-server
MCP server for Jira — search, create, update, transition issues, manage projects, boards, and spr... Runs locally from the @supernova123/jira-mcp-server npm package.
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.