Model Context Protocol (MCP) server for Jira Cloud - enables AI assistants to interact with Jira
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.
JIRA_API_TOKENAPI keyrequiredJira API token (generate at https://id.atlassian.com/manage/api-tokens)
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
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_healthRun a data quality health check on a project backlog — surfaces rot, staleness, and planning gapsRun a data quality health check on a project backlog — surfaces rot, staleness, and planning gaps
No input schema was published for this tool.
projectJira project key (e.g. PROJ, ENG)Jira project key (e.g. PROJ, ENG)
No input schema was published for this tool.
contributor_workloadPer-contributor workload breakdown with staleness and risk — scopes detail queries to fit within sample capPer-contributor workload breakdown with staleness and risk — scopes detail queries to fit within sample cap
No input schema was published for this tool.
sprint_reviewSprint review preparation — velocity, scope changes, at-risk items, and completion forecastSprint review preparation — velocity, scope changes, at-risk items, and completion forecast
No input schema was published for this tool.
board_idJira board ID (find via manage_jira_board list)Jira board ID (find via manage_jira_board list)
No input schema was published for this tool.
narrow_analysisRefine a capped analysis query — guides you to narrow JQL for precise detail metricsRefine a capped analysis query — guides you to narrow JQL for precise detail metrics
No input schema was published for this tool.
jqlThe JQL query to refine (from a previous capped analysis)The JQL query to refine (from a previous capped analysis)
No input schema was published for this tool.
manage_jira_filterSearch for issues using JQL queries, or manage saved filters. Returns issue details (title, status, description). For quantitative questions (counts, totals, overdue, workload), use analyze_jira_issues instead.Search for issues using JQL queries, or manage saved filters. Returns issue details (title, status, description). For quantitative questions (counts, totals, overdue, workload), use analyze_jira_issues instead.
No input schema was published for this tool.
manage_jira_sprintManage sprints: create, start, close, and assign issues to sprintsManage sprints: create, start, close, and assign issues to sprints
No input schema was published for this tool.
manage_jira_issueGet, create, update, delete, move, transition, comment on, link, log work on, or explore hierarchy of Jira issues. For custom-field writes, consult `jira://capabilities` (field routing) and `jira://custom-fields/{projectKey}/{issueType}` (what is settable here) — some fields need dedicated tools an…Get, create, update, delete, move, transition, comment on, link, log work on, or explore hierarchy of Jira issues. For custom-field writes, consult `jira://capabilities` (field routing) and `jira://custom-fields/{projectKey}/{issueType}` (what is settable here) — some fields need dedicated tools an…
No input schema was published for this tool.
manage_jira_projectList projects or get project configuration and metadata. For issue counts, workload, or cross-project comparison, use analyze_jira_issues with metrics: ["summary"] instead.List projects or get project configuration and metadata. For issue counts, workload, or cross-project comparison, use analyze_jira_issues with metrics: ["summary"] instead.
No input schema was published for this tool.
manage_jira_boardList boards or get board details and configurationList boards or get board details and configuration
No input schema was published for this tool.
analyze_jira_issuesNo description publishedThis tool published no description. Forge does not invent one.
manage_jira_planNavigate and manage the strategic-to-execution hierarchy. Walks issue trees and Atlassian Goals via GraphQL. Read: analyze rollups (dates, points, progress, conflicts), discover goals (list_goals), get goal detail (get_goal). Write: create/update goals, post status updates, link/unlink Jira issues…Navigate and manage the strategic-to-execution hierarchy. Walks issue trees and Atlassian Goals via GraphQL. Read: analyze rollups (dates, points, progress, conflicts), discover goals (list_goals), get goal detail (get_goal). Write: create/update goals, post status updates, link/unlink Jira issues…
No input schema was published for this tool.
manage_jira_mediaManage file attachments on Jira issues (remote). Operations here affect Jira — delete permanently removes an attachment from the issue for all users. Use manage_workspace for local file staging. Downloads copy from Jira to workspace; uploads copy from workspace to Jira.Manage file attachments on Jira issues (remote). Operations here affect Jira — delete permanently removes an attachment from the issue for all users. Use manage_workspace for local file staging. Downloads copy from Jira to workspace; uploads copy from workspace to Jira.
No input schema was published for this tool.
manage_workspaceManage files in the local workspace staging area (local only — no Jira impact). Files downloaded via manage_jira_media land here. Delete only removes the local copy. Use manage_jira_media to affect attachments on Jira issues.Manage files in the local workspace staging area (local only — no Jira impact). Files downloaded via manage_jira_media land here. Delete only removes the local copy. Use manage_jira_media to affect attachments on Jira issues.
No input schema was published for this tool.
queue_jira_operationsExecute multiple Jira operations in a single call. Operations run sequentially with result references ($0.key) and per-operation error strategies (bail/continue). Powerful for analysis pipelines: create a filter, then run multiple analyze_jira_issues calls against $0.filterId with different groupBy…Execute multiple Jira operations in a single call. Operations run sequentially with result references ($0.key) and per-operation error strategies (bail/continue). Powerful for analysis pipelines: create a filter, then run multiple analyze_jira_issues calls against $0.filterId with different groupBy…
No input schema was published for this tool.
16 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.
Model Context Protocol (MCP) server for Jira Cloud - enables AI assistants to interact with Jira
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
67 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+55 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.