Labsco
MCP SERVER

Jira

by cfdude

Drive Jira from an assistant: file and re-order tickets, hang them off epics, walk a sprint through its states, and read the release and component progress that follows.

Project & Task ManagementVerified
Summary
Ticket hygiene and agile reporting stop being separate errands.

With the instance mapping in place, an agent can file the ticket, park it under an epic, drop it into the running sprint, and then answer how that sprint is tracking. The instance and working_dir arguments are not optional in practice, so the mapping file is where a setup succeeds or fails. Roadmap-level plan tools depend on Jira Premium, and confluence_health_check answers for a different server altogether.

What it is

A multi-instance Jira client whose tool set covers issues, agile boards, epics, versions, components, JQL and Premium strategic planning.

What you get
  • Issue handling from creation to deletion, with comments, workflow moves taken from the transition IDs a lookup supplies, bulk field updates over a set of keys, relative ranking and estimates.
  • Sprints: open one, add issue keys, switch it to active with dates attached, close it when the work lands, and read its detail at any point.
  • Boards for a project, together with column configuration, current metrics and quickfilter details.
  • Epic structure, where a single operation can produce the epic and its children at once, while other calls reparent issues, order epics and list what an epic contains.
  • Reporting data an agent can compare: a per-sprint report, velocity over a number of sprints, burndown for one sprint and cumulative flow for a board.
  • Version and component records on a project, each carrying its own progress and completion breakdown.
  • The search and setup surface: JQL queries, saved filters, project lookup, workflow statuses, issue types, and the custom field IDs the config file wants.
  • Premium plans: create, fetch, patch, duplicate, archive or trash a plan, and manage the teams sitting on it.
Requirements

A Jira instance configured in .jira-config.json with its project mapping, since the instance name and a working_dir path travel with every call; detect_project_fields resolves the custom field IDs that file needs. Plans require Jira Premium, and removing an issue outright requires the Delete Issues permission.

Setup effort

One command plus a key — npm install -g jira-server, then supply credentials