Labsco
MCP SERVER

JIRA

by Dsazz ↗

Work JIRA from your editor — assigned issues, JQL search, create and transition issues, comments and worklogs — with everything returned as readable markdown.

Project & Task Management
Summary
The array operations are the detail that saves you.

Updating labels or components takes an explicit add, remove or set — so an assistant adding one label does not silently drop the other four, which is the classic way a well-meaning bulk update damages a board. Worth knowing that the same token creates issues and transitions status, so this is a full participant in your project, not a reader of it.

What it is

An MCP server for Atlassian JIRA covering the full issue lifecycle plus the project, board and sprint structure around it. Results come back as formatted markdown with issue previews and links, so the assistant's answer is readable rather than a dump of API JSON.

What you get
  • The daily loop — `jira_get_assigned_issues` with no parameters, `jira_get_issue` by key, `jira_get_current_user`
  • `search_jira_issues` — JQL when you know it, or plain helper parameters when you do not
  • `jira_create_issue` — required `projectKey`, `issueType` and `summary`, plus optional description, priority, assignee, reporter, labels, components, fix and affects versions, time estimate, due date, environment and custom fields
  • `jira_update_issue` — field changes, a `status` transition, and array operations on labels, components and versions that add, remove or set rather than overwriting blindly
  • Comments — `jira_get_issue_comments` with author filtering and date ranges
  • Time tracking — `jira_add_worklog`, `jira_get_worklogs` with date filtering, `jira_update_worklog`, `jira_delete_worklog`
  • Structure — `jira_get_projects`, `jira_get_boards` for Scrum and Kanban, `jira_get_sprints`
  • Atlassian Document Format parsed so rich descriptions read as text
Requirements

A JIRA Cloud site and an API token, generated at Atlassian's API token page. Three environment variables: `JIRA_HOST` as your full `https://your-domain.atlassian.net` URL, `JIRA_USERNAME` as the email you sign in with, and `JIRA_API_TOKEN`. Tokens can contain an `=` sign — paste it on one line with no quotes around it, which is the mistake that most often makes the first connection fail. Run it with `bunx -y @dsazz/mcp-jira@latest`. Package `@dsazz/mcp-jira`, MIT.

Setup effort

One command plus a key — bunx -y @dsazz/mcp-jira@latest, then supply credentials