jira_get_assigned_issuesLABSCO 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_issueswith no parameters,jira_get_issueby key,jira_get_current_user search_jira_issues— JQL when you know it, or plain helper parameters when you do notjira_create_issue— requiredprojectKey,issueTypeandsummary, plus optional description, priority, assignee, reporter, labels, components, fix and affects versions, time estimate, due date, environment and custom fieldsjira_update_issue— field changes, astatustransition, and array operations on labels, components and versions that add, remove or set rather than overwriting blindly- Comments —
jira_get_issue_commentswith author filtering and date ranges - Time tracking —
jira_add_worklog,jira_get_worklogswith date filtering,jira_update_worklog,jira_delete_worklog - Structure —
jira_get_projects,jira_get_boardsfor 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
USE CASES
01
Starting the day without opening JIRA
Ask what is assigned to you and read the list as markdown with links straight into the issues.
02
Filing a bug properly the first time
Create it with priority, assignee, labels and a time estimate in one call instead of editing it four times afterwards.
03
Moving work along after a standup
Transition the status and add the label without disturbing the labels already on the issue.
04
Logging the time you actually spent
Add worklog entries as you go, and correct them later when the estimate turns out wrong.
05
Catching up on a long-running ticket
Pull the comments filtered by author or date range instead of scrolling the whole thread.
14 tools
Listed in project docs. Your client may show a different list.
jira_get_issuejira_get_issue_commentsjira_create_issuejira_update_issuejira_get_projectsjira_get_boardsjira_get_sprintsjira_add_worklogjira_get_worklogsjira_update_worklogjira_delete_worklogjira_get_current_usersearch_jira_issuesBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
- bunx on PATH
- JIRA_API_TOKEN in your environment
- JIRA_HOST in your environment
- JIRA_USERNAME in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
bunx -y @dsazz/mcp-jira@latestMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"JIRA Tools": {
"command": "bunx",
"args": [
"-y",
"@dsazz/mcp-jira@latest"
],
"env": {
"JIRA_HOST": "https://<YOUR_DOMAIN>.atlassian.net",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>"
}
}
}
}Cursor — local build
This tab runs a local build: git clone https://github.com/Dsazz/mcp-jira.git, then bun install and bun run build in the clone, and point args at its dist/index.js.
CURSOR — LOCAL BUILD · JSON
{
"mcpServers": {
"JIRA Tools": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROJECT>/dist/index.js"
],
"env": {
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"JIRA_HOST": "https://<YOUR_JIRA_HOST>.atlassian.net"
}
}
}
}
