io.github.aaronsb/jira-cloud

MCPattested
v0.10.0io.github.aaronsbUnknownUpdated 6mo agonpmGitHub

MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields

A Model Context Protocol server for interacting with Jira Cloud instances. Download and open it — Claude Desktop will prompt for your Jira credentials. Generate an API token at Atlassian Account Settings. ------|-------------| | Get, create, update, delete, move, transition, comment on, link, or traverse hierarchy of issues | | Search for issues using JQL queries, or manage saved filters | | List…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
4GitHub stars
6mo agoLast update
Package
Authorio.github.aaronsb
LicenseUnknown
Version0.10.0
Sourcemcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · ab7884a
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface17 tools · none privileged
Security scan✓ Cleanv0.11.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

17 tools · none privileged
Statically extracted from the published packagev0.11.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

backlog_healthNo description published

This tool published no description. Forge does not invent one.

projectNo description published

This tool published no description. Forge does not invent one.

contributor_workloadNo description published

This tool published no description. Forge does not invent one.

sprint_reviewNo description published

This tool published no description. Forge does not invent one.

board_idNo description published

This tool published no description. Forge does not invent one.

narrow_analysisNo description published

This tool published no description. Forge does not invent one.

jqlNo description published

This tool published no description. Forge does not invent one.

manage_jira_filterNo description published

This tool published no description. Forge does not invent one.

manage_jira_sprintNo description published

This tool published no description. Forge does not invent one.

manage_jira_issueNo description published

This tool published no description. Forge does not invent one.

manage_jira_projectNo description published

This tool published no description. Forge does not invent one.

manage_jira_boardNo description published

This tool published no description. Forge does not invent one.

analyze_jira_issuesNo description published

This tool published no description. Forge does not invent one.

manage_jira_planNo description published

This tool published no description. Forge does not invent one.

manage_jira_mediaNo description published

This tool published no description. Forge does not invent one.

manage_workspaceNo description published

This tool published no description. Forge does not invent one.

queue_jira_operationsNo description published

This tool published no description. Forge does not invent one.

0 of 17 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A Model Context Protocol server for interacting with Jira Cloud instances. Download and open it — Claude Desktop will prompt for your Jira credentials. Generate an API token at Atlassian Account Settings. ------|-------------| | Get, create, update, delete, move, transition, comment on, link, or traverse hierarchy of issues | | Search for issues using JQL queries, or manage saved filters | | List projects or get project configuration and metadata | | List boards or get board details and…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in cloud platforms