jira_add_comment
Add a comment to a Jira issue
LABSCO SUMMARY
Triage happens in the editor, and the ticket is already filled in when it lands.
The 12 tools cover one loop tightly — find work with JQL, read it, change it, hand it to someone, say why — and jira_create_issue takes enough fields that a ticket filed from here does not need editing afterwards. There is a sharp edge worth knowing before you wire it into an agent: jira_delete_issue deletes permanently, and it sits in the same tool set as the read calls. Boards, sprints and worklogs are outside this surface; it is issues, comments and projects.
What it is
A Jira server covering the issue lifecycle — JQL search, create, update, assign, comment, delete — against a self-supplied base URL
What you get
- JQL search with a result cap, so 'project = PROJ AND status = Open' or 'assignee = currentUser() AND status != Done' runs from the chat (jira_search_issues).
- Issue creation carrying project key, issue type, summary, description, priority, labels, components, assignee and custom fields (jira_create_issue).
- Updates that include status transitions, plus assignment and permanent deletion (jira_update_issue, jira_assign_issue, jira_delete_issue).
- The comment thread in both directions: read every comment on an issue, add one (jira_get_comments, jira_add_comment).
- Project context needed before filing: the project list, one project's details, and the issue types that project accepts (jira_get_projects, jira_get_project, jira_get_issue_types).
- Identity of the authenticated account, which is what makes currentUser() queries meaningful (jira_get_current_user).
Requirements
A Jira instance you can reach and an account on it: JIRA_BASE_URL and JIRA_PAT.
Setup effort
One command plus credentials — npx mcp-jira-server, then supply credentials
USE CASES
01
Clearing a queue of unassigned bugs
One JQL query returns the queue, each issue is handed to an owner, and the reason it went to them is left on the ticket rather than in a chat window.
02
Filing a ticket properly without switching windows
The project list and its accepted issue types come back first, so the issue is created with the right type, priority, labels, components and custom fields in one go.
03
Catching up on a ticket before standup
The issue and its full comment thread read back together, which is usually the whole context needed to say something useful about it.
04
Closing out the work you just finished
The same update call moves status, adjusts fields and reassigns, and a comment records what actually changed while the detail is still fresh.
12 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
jira_assign_issue
Assign a Jira issue to a user
jira_create_issue
Create a new Jira issue in a specified project
jira_delete_issue
Delete a Jira issue permanently
jira_get_comments
Get all comments from a Jira issue
jira_get_current_user
Get information about the currently authenticated user
jira_get_issue
Get details of a specific Jira issue by its key (e.g., PROJ-123)
jira_get_issue_types
Get available issue types for a project
jira_get_project
Get details of a specific Jira project
jira_get_projects
List all available Jira projects
jira_search_issues
Search for Jira issues using JQL (Jira Query Language). Examples: "project = PROJ AND status = Open", "assignee = currentUser() AND status != Done"
jira_update_issue
Update an existing Jira issue
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools when we connected. Status transitions go through jira_update_issue's status parameter. jira_delete_issue is permanent and irreversible.
Requires
- npx on PATH
- Node.js 18 or later
- JIRA_PAT in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 12 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx mcp-jira-serverMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"-y",
"mcp-jira-server"
],
"env": {
"JIRA_BASE_URL": "https://jira.domain.com",
"JIRA_PAT": "<YOUR_JIRA_PAT>"
}
}
}
}VS Code — npx
VS CODE — NPX · JSON
{
"servers": {
"jira": {
"command": "npx",
"args": [
"-y",
"mcp-jira-server"
],
"env": {
"JIRA_BASE_URL": "https://jira.domain.com",
"JIRA_PAT": "<YOUR_JIRA_PAT>"
}
}
}
}VS Code — local build
Clone and build the server
VS CODE — LOCAL BUILD · TERMINAL
git clone https://github.com/edrich13/mcp-jira-server.git
cd mcp-jira-server
npm install
npm run buildCreate or update .vscode/mcp.json in your workspace
<YOUR_PATH_TO_MCP_JIRA_SERVER> is the folder you cloned into.
VS CODE — LOCAL BUILD · JSON
{
"servers": {
"jira": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_JIRA_SERVER>/build/index.js"
],
"env": {
"JIRA_BASE_URL": "https://jira.domain.com",
"JIRA_PAT": "<YOUR_JIRA_PAT>"
}
}
}
}
