get_user
Get user's account ID by email
LABSCO SUMMARY
The everyday issue loop, handed to the agent.
It covers what a project lead delegates most: pull a project's issues with JQL, create them and their subtasks, link the ones that block each other, reassign, clean up. Two lookups make the writes land — get_user turns an email into the account ID Jira wants for an assignee, and the link-type list gives the exact name a dependency needs. The README documents nothing for sprints, boards or epics, and the server talks to one site at a time.
What it is
A TypeScript server over Jira's REST API for one Jira site, the one JIRA_HOST names. It is not published to a package registry: you clone it, build it, and point your client at build/index.js.
What you get
- An account ID looked up from an email address — get_user — so an issue can be assigned
- The issue types and issue link types your site defines, listed before you create or link anything
- A project's issues, all of them or filtered with JQL
- Issues and subtasks created with summary, description, type, assignee, labels, components and priority, and updated later — status included
- Dependencies recorded as issue links, such as one issue blocking another
- One issue, an issue with its subtasks, or a list of issues deleted in a single call
- Descriptions written with blank-line paragraphs, bullets, numbered lists and headers
Requirements
A Jira site and an API token: JIRA_HOST, JIRA_API_TOKEN and JIRA_EMAIL for basic auth, or a Personal Access Token in JIRA_API_TOKEN with JIRA_AUTH_TYPE=bearer. Node.js and npm to build it from the clone.
Setup effort
Build from source — git clone https://github.com/George5562/Jira-MCP-Server.git
USE CASES
01
Assigning a new issue to the right person
Look up a teammate's account ID from their email with get_user, then create the issue with that ID as its assignee. The README pairs this with a note in your project listing who works on what, so the model can pick the person.
02
Splitting a task into subtasks
Create the parent issue, then subtasks under it, each with its own summary, description and assignee. Deleting the parent can take its subtasks with it in the same call.
03
Recording what blocks what
Read the link types your site defines, then link the blocking issue to the one it blocks, so the dependency shows up in Jira itself.
04
Pulling up the work in progress
List a project's issues filtered with JQL — by status, by assignee, newest first — and hand the result to the model to plan or schedule from.
2 tools
Listed in project docs. Your client may show a different list.
list_link_types
List all available issue link types
BEFORE YOU INSTALL
What to know first
Requires
- Node.js and npm
- JIRA_HOST in your environment
- JIRA_API_TOKEN in your environment
- JIRA_EMAIL in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/George5562/Jira-MCP-Server.git
cd Jira-MCP-Server
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"jira-server": {
"command": "<YOUR_PATH_TO_NODE>",
"args": [
"<YOUR_PATH_TO_JIRA_SERVER>/build/index.js"
],
"cwd": "<YOUR_PATH_TO_JIRA_SERVER>",
"env": {
"JIRA_HOST": "<YOUR_JIRA_INSTANCE>.atlassian.net",
"JIRA_EMAIL": "<YOUR_JIRA_EMAIL>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"JIRA_AUTH_TYPE": "basic"
}
}
}
}<YOUR_PATH_TO_JIRA_SERVER> is the absolute path of the Jira-MCP-Server folder you cloned, and <YOUR_PATH_TO_NODE> is the path that which node (or where node on Windows) prints. For a Personal Access Token, set JIRA_AUTH_TYPE to bearer, put the token in JIRA_API_TOKEN and leave out JIRA_EMAIL.
Cursor
CURSOR · JSON
{
"mcpServers": {
"jira-mcp-server": {
"command": "node",
"args": [
"<YOUR_PATH_TO_JIRA_MCP_SERVER>/build/index.js"
],
"cwd": "<YOUR_PATH_TO_JIRA_MCP_SERVER>",
"env": {
"JIRA_HOST": "<YOUR_JIRA_INSTANCE>.atlassian.net",
"JIRA_EMAIL": "<YOUR_JIRA_EMAIL>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"JIRA_AUTH_TYPE": "basic"
}
}
}
}<YOUR_PATH_TO_JIRA_MCP_SERVER> is the absolute path of the folder you cloned. For a Personal Access Token, set JIRA_AUTH_TYPE to bearer, put the token in JIRA_API_TOKEN and leave out JIRA_EMAIL.
