search_issuesLABSCO SUMMARY
JQL is the tool that makes the rest worth having.
Reading and creating single issues is table stakes; passing JQL straight through means the assistant can express the query you would have written yourself, and everything downstream operates on that result. Two things to check on day one: the token has to belong to an account with permission on the project, and status transitions in Jira are workflow-constrained, so an update that sets a status the workflow disallows will fail on Jira's side rather than in the tool.
What it is
An MCP server for Jira. Six tools cover the daily loop — find issues with JQL, read one, create a new one, change an existing one, add a comment, and look up project information — with authentication through a Jira API token rather than a password.
What you get
search_issuesruns a JQL query, which is what makes 'open issues in this project' one call rather than a filter you maintainget_issuereturns the details of a specific issuecreate_issueopens a new one, andupdate_issuechanges the title, description, status or assignee of an existing oneadd_commentposts a comment to an issueget_project_inforeturns project information- A default project through
DEFAULT_PROJECT_KEY, so a request that does not name one still lands somewhere sensible
Requirements
Node.js, and a Jira API token created under account settings. Configuration is JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN and DEFAULT_PROJECT_KEY. After npm install, npm run setup runs an interactive setup that collects the connection details and writes both the environment file and a Claude Desktop configuration; setting them by hand is also supported. The client then launches the server entry point with node, with the four variables in its environment.
Setup effort
Build from source
USE CASES
01
Finding the issues that actually need attention
Ask in words, let it become a JQL query, and read the result without maintaining a saved filter.
02
Filing an issue as soon as it comes up
Create it in the conversation where the problem was found instead of switching context.
03
Moving work along
Change the status or reassign the issue without opening the board.
04
Leaving a note on a ticket
Post the update as a comment so the history stays in Jira.
6 tools
Listed in project docs. Your client may show a different list.
get_issuecreate_issueupdate_issueadd_commentget_project_infoBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- JIRA_API_TOKEN in your environment
- JIRA_USERNAME in your environment
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/SunWooBang/jira-mcp-server
cd jira-mcp-server
npm install
npm run setupMCP Clients
Claude Desktop — Windows
CLAUDE DESKTOP — WINDOWS · JSON
{
"mcpServers": {
"jira": {
"command": "node",
"args": [
"<YOUR_PATH_TO_JIRA_MCP_SERVER>\\index.js"
],
"env": {
"JIRA_URL": "https://<YOUR_DOMAIN>.atlassian.net",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"DEFAULT_PROJECT_KEY": "PROJ"
}
}
}
}<YOUR_PATH_TO_JIRA_MCP_SERVER> is the full path of your clone. The README points at index.js, but package.json starts the server from server\index.js, so use …\jira-mcp-server\server\index.js if the root file is missing. Set JIRA_URL to your Atlassian site, JIRA_USERNAME to your Jira account email, JIRA_API_TOKEN to an API token created under your Atlassian account settings > Security, and DEFAULT_PROJECT_KEY to your project key.
Claude Desktop — macOS
CLAUDE DESKTOP — MACOS · JSON
{
"mcpServers": {
"jira": {
"command": "node",
"args": [
"<YOUR_PATH_TO_JIRA_MCP_SERVER>/index.js"
],
"env": {
"JIRA_URL": "https://<YOUR_DOMAIN>.atlassian.net",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"DEFAULT_PROJECT_KEY": "PROJ"
}
}
}
}<YOUR_PATH_TO_JIRA_MCP_SERVER> is the full path of your clone. The README points at index.js, but package.json starts the server from server/index.js, so use …/jira-mcp-server/server/index.js if the root file is missing. Set JIRA_URL to your Atlassian site, JIRA_USERNAME to your Jira account email, JIRA_API_TOKEN to an API token created under your Atlassian account settings > Security, and DEFAULT_PROJECT_KEY to your project key.
