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…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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 publishedThis tool published no description. Forge does not invent one.
projectNo description publishedThis tool published no description. Forge does not invent one.
contributor_workloadNo description publishedThis tool published no description. Forge does not invent one.
sprint_reviewNo description publishedThis tool published no description. Forge does not invent one.
board_idNo description publishedThis tool published no description. Forge does not invent one.
narrow_analysisNo description publishedThis tool published no description. Forge does not invent one.
jqlNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_filterNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_sprintNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_issueNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_projectNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_boardNo description publishedThis tool published no description. Forge does not invent one.
analyze_jira_issuesNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_planNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_mediaNo description publishedThis tool published no description. Forge does not invent one.
manage_workspaceNo description publishedThis tool published no description. Forge does not invent one.
queue_jira_operationsNo description publishedThis 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.
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…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.