jira_add_attachment
Attach a file to a Jira issue.
LABSCO SUMMARY
The transition handling is the tell that someone used this on a real board: call jira_transition_issue with the key alone, read back the moves legal from where the issue sits, then commit one.
Jira transition ids are workflow-specific, so a tool that demanded one up front would be unusable to an agent that cannot see the board — discovering them in the same call is what turns 'move this to review' into a single instruction. Around that sits a competent lifecycle set, with assignment routed through jira_search_users so an accountId is resolved before it is written. Board-level work is the thin part: jira_list_sprints reads a board's sprints for a boardId, and nothing here creates, starts or closes one.
What it is
A Jira client covering the issue lifecycle — JQL search, read, create, update, transition, assign, comment, subtasks, worklogs and attachments — with project, sprint and user lookups alongside it.
What you get
- Search and read: jira_list_issues takes a jql string and a limit and returns key, summary, status and assignee per issue; jira_get_issue returns one issueKey in full, including description, priority and comments.
- Creating and editing: jira_create_issue takes projectKey, issueType, summary, description, priority and assigneeId and returns the new key; jira_update_issue changes summary, description, priority and assignee on an existing issue; jira_create_subtask creates the same under a parentKey.
- Workflow moves that respect the workflow: jira_transition_issue called with issueKey alone returns the transitions available from the issue's current status, and the same call with a transitionId performs the move.
- People: jira_search_users resolves a name or email to an accountId and displayName, jira_assign_issue sets that accountId or clears it with null, and jira_myself returns the account the session is authenticated as.
- Context lookups: jira_list_projects returns key, name, lead and style for the projects the account can reach, and jira_list_sprints returns a board's sprints for a boardId, filtered by state.
- Bookkeeping on an issue: jira_add_comment posts a body, jira_add_worklog records timeSpent with a comment, and jira_add_attachment uploads a local filePath onto the issue.
Requirements
A Jira site and an account authenticated against it: jira_myself resolves the current authenticated user, and jira_list_projects returns the projects that account can reach.
Setup effort
Follow the published steps — npm install -g jira-pilot
USE CASES
01
Triaging what landed on the board overnight
Pull the queue with a JQL filter, open the ones that need a decision, and move them on without leaving the session.
02
Filing a bug properly at the moment you find it
Create the issue against the right project, put it on the right person, and attach the log or screenshot while you still have it.
03
Breaking a ticket that grew too big into pieces
Split the work into subtasks under the parent and trim the parent's description down to what is left of it.
04
Closing out the day on the tickets you touched
Log the time against each issue, leave the note that explains it, and move anything finished into its next status.
05
Handing a ticket to the right person
Turn a name or an email into the account id Jira wants, set it on the issue, or clear it when the work goes back to the pool.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
jira_add_comment
Add a comment to a Jira issue.
jira_add_worklog
Log work to a Jira issue.
jira_assign_issue
Assign or unassign a Jira issue. Use accountId to assign, or null to unassign.
jira_create_issue
Create a new Jira issue in a project. Returns the created issue key.
jira_create_subtask
Create a subtask for a parent issue.
jira_get_issue
Get full details of a specific Jira issue including summary, description, status, assignee, priority, and comments.
jira_list_issues
List Jira issues using JQL. Returns key, summary, status, and assignee for each issue.
jira_list_projects
List all accessible Jira projects. Returns project key, name, lead, and style.
jira_list_sprints
List sprints for a Jira board. Requires a board ID.
jira_myself
Get details about the current authenticated user.
jira_search_users
Search for Jira users by name or email. Returns accountId and displayName.
jira_transition_issue
Transition a Jira issue to a new status. First call with only issueKey to see available transitions, then call again with the transitionId.
jira_update_issue
Update an existing Jira issue. Supports updating summary, description, priority, and assignee.
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected. Bulk transition, assign and label, sprint start and complete, git branch creation and the AI commands are CLI-only and not available over MCP.
Requires
Node.js 20.0.0 or higher
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Install it globally — this puts the jira command on your PATH
TERMINAL
npm install -g jira-pilotSet up your credentials — it prompts for your Jira Site URL, your Atlassian account email and an API Token from https://id.atlassian.com/manage-profile/security/api-tokens
TERMINAL
jira config setupMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"-y",
"jira-pilot",
"mcp"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"jira-pilot": {
"command": "jira",
"args": [
"mcp"
]
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"jira-pilot": {
"command": "jira",
"args": [
"mcp"
]
}
}
}
