jira-dc-advops-mcp

Local MCP helpers for Jira Data Center advanced ops used from Cursor.

Русская документация: README.ru.md.

Capabilities:

1. Tempo Structure — read / update boards (hierarchy + column values) via /rest/structure/2.0/*

2. Agile Kanban / Scrum — board columns + issue placement via /rest/agile/1.0/* (daily standup reports)

Talks to the same proxy/auth as @atlassian-dc-mcp/jira (local TLS proxy + token from keychain / env). Prefer these tools over ad-hoc curl to the public Jira hostname.

• structureId from StructureBoard.jspa?s=<id>

• boardId from RapidBoard.jspa?rapidView=<id>

Auth

Same sources as @atlassian-dc-mcp/jira:

• JIRA_HOST (env or ~/.atlassian-dc-mcp/jira.env) — typically your local proxy, e.g. https://localhost:8444

• JIRA_API_TOKEN (env), or macOS Keychain service atlassian-dc-mcp / account jira-token

Do not commit tokens or *.env files. See SECURITY.md.

Related MCP server: MCP Atlassian Node Server

Tools — Structure (read)

Tools — Structure (write)

Tools — Agile boards (read)

Daily standup snapshot

agile_listBoards
  name: "Team"
  type: kanban

agile_getBoardSnapshot
  boardId: 123
  jql: "assignee = currentUser() AND resolution = EMPTY"
  excludeColumns: ["Done"]
  # includeBacklog: false (default) — skip fabricated kanban Backlog column

Returns ordered columns with compact issues (key, summary, status, column, assignee, …).

Column placement = issue status id mapped through board configuration. For kanban, the board subQuery is ANDed by default so the set closer matches what the UI shows.

Locate specific issues

agile_locateIssues
  boardId: 123
  issueKeys: ["PROJ-1", "PROJ-2"]

Add issues under a Structure folder

structure_listFolders
  structureId: 123

structure_addIssues
  structureId: 123
  folderName: "My folder"   # or underRowId: <rowId>
  issueKeys: ["PROJ-1", "PROJ-2"]
  # skipIfPresent: true (default)

Uses POST /rest/structure/2.0/forest/update with action: add. Resolves issue keys → numeric ids. Skips issues already direct children of the parent unless skipIfPresent: false.

Fast path for a Structure Board

structure_getBoard
  structureId: 123
  # optional attributes override; default: key, summary, status, issuetype

Returns nested { rowId, depth, issueId?, itemType?, values, children[] }.

Generators / loop markers are included unless includeGenerators: false.

Forest formula

Structure returns a serialized formula. This MCP parses it into rows:

rowId:depth:itemIdentity where itemIdentity is either an issue id (14707) or a typed id (5/240 → folder / generator / … via itemTypes).

Cursor config

"jira-dc-advops": {
  "command": "node",
  "args": ["/path/to/jira-dc-advops-mcp/index.js"],
  "env": {
    "JIRA_HOST": "https://localhost:8444",
    "NODE_TLS_REJECT_UNAUTHORIZED": "0"
  }
}

After changing index.js / agile.js, reload MCP servers in Cursor so new tools appear.

Notes

• Forest write beyond structure_addIssues (move/remove rows, create folders) is not exposed yet.

• For issue details beyond board columns (Status Comment, links, …), use user-jira-dc (jira_getIssue / JQL).

• Large boards: prefer *ToFile tools over stuffing full payloads into chat.

• Agile tools do not move issues between columns (that is a workflow transition — use user-jira-dc).