Jira MCP Server
Enables interaction with Atlassian Jira Cloud through its REST API, providing tools to read, create, update, and delete Jira resources including projects, issues, comments, and workflows. Supports JQL queries, issue management, and full CRUD operations across Jira API endpoints.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Jira MCP Server show me all open issues assigned to me in the DEV project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Jira MCP Server
A Model Context Protocol (MCP) server for interacting with Atlassian Jira. Connect AI assistants like Claude, Cursor AI, and others directly to your Jira projects, issues, and workflows.
Prerequisites
Node.js (version 18 or higher)
Atlassian Jira account with:
API token - Generated from Atlassian API Tokens
Site name - Your Jira organization name (e.g.,
mycompanyformycompany.atlassian.net)
Installation
Via npm (recommended)
npm install -g jira-mcp-serverFrom Source
Install dependencies:
npm installBuild the project:
npm run buildConfigure your MCP client (see below)
Configuration
For Cursor Users
Add this to your Cursor MCP configuration (~/.cursor/mcp.json):
{
"mcpServers": {
"Jira MCP": {
"command": "node",
"args": [
"/path/to/mcp-server-atlassian-jira/dist/index.js"
],
"env": {
"ATLASSIAN_SITE_NAME": "your-company",
"ATLASSIAN_USER_EMAIL": "your.email@company.com",
"ATLASSIAN_API_TOKEN": "your_api_token"
}
}
}
}Restart Cursor to activate.
For Claude Desktop Users
Add this to your Claude configuration file (~/.claude/claude_desktop_config.json):
{
"mcpServers": {
"jira": {
"command": "node",
"args": [
"/path/to/mcp-server-atlassian-jira/dist/index.js"
],
"env": {
"ATLASSIAN_SITE_NAME": "your-company",
"ATLASSIAN_USER_EMAIL": "your.email@company.com",
"ATLASSIAN_API_TOKEN": "your_api_token"
}
}
}
}Restart Claude Desktop to activate.
Available Tools
jira_get- Read data from any Jira API endpointjira_post- Create resources (issues, comments, etc.)jira_put- Replace resourcesjira_patch- Partially update resourcesjira_delete- Delete resourceshealth_check- Verify server configuration and connectivity
Common Use Cases
Ask your AI assistant:
"List all projects I have access to"
"Show me issues assigned to me that are in progress"
"Find all high priority issues in the DEV project"
"Get full details about issue PROJ-456 including comments"
"Add a comment to PROJ-456: 'Code review completed'"
"Create a new bug in the MOBILE project"
Troubleshooting
Authentication Issues
Verify your API token is active at Atlassian API Tokens
Check your site name format:
https://mycompany.atlassian.net→ site name ismycompanyTest credentials:
node dist/index.js get --path "/rest/api/3/myself"
Common Errors
403 Forbidden: Check API token permissions
404 Not Found: Verify project keys and issue IDs are correct
No results: Try broader search criteria or validate JQL syntax
Integration Issues
Cursor: Restart Cursor after updating
~/.cursor/mcp.jsonClaude Desktop: Restart Claude Desktop after updating config file
FAQ
What permissions do I need?
Your Atlassian account needs access to Jira with appropriate project permissions.
Does this work with Jira Server?
Currently supports Jira Cloud only.
Is my data secure?
Yes! This tool runs entirely on your local machine and uses your own Jira credentials.
Available Tools
6 toolshealth_checkHealth checkC
Verify Jira MCP server configuration and connectivity.
Inputs: siteName.
jira_deleteJira DELETE RequestA
Delete Jira resources. Returns TOON format by default.
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Delete issue:
/rest/api/3/issue/{issueIdOrKey}Query param:deleteSubtasks=trueto delete subtasksDelete comment:
/rest/api/3/issue/{issueIdOrKey}/comment/{commentId}Delete worklog:
/rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId}Delete attachment:
/rest/api/3/attachment/{attachmentId}Remove watcher:
/rest/api/3/issue/{issueIdOrKey}/watchersQuery param:accountId={accountId}
Note: Most DELETE endpoints return 204 No Content on success.
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Inputs: path (required), queryParams, jq, outputFormat.
jira_getJira GET RequestA
Read any Jira data. Returns TOON format by default (30-60% fewer tokens than JSON).
IMPORTANT - Cost Optimization:
ALWAYS use
jqparam to filter response fields. Unfiltered responses are very expensive!Use
maxResultsquery param to restrict result count (e.g.,maxResults: "5")If unsure about available fields, first fetch ONE item with
maxResults: "1"and NO jq filter to explore the schema, then use jq in subsequent calls
Schema Discovery Pattern:
First call:
path: "/rest/api/3/search/jql", queryParams: {"maxResults": "1", "jql": "project=PROJ"}(no jq) - explore available fieldsThen use:
jq: "issues[*].{key: key, summary: fields.summary, status: fields.status.name}"- extract only what you need
Output format: TOON (default, token-efficient) or JSON (outputFormat: "json")
Common paths:
/rest/api/3/project- list all projects/rest/api/3/project/{projectKeyOrId}- get project details/rest/api/3/search/jql- search issues with JQL (usejqlquery param). NOTE:/rest/api/3/searchis deprecated!/rest/api/3/issue/{issueIdOrKey}- get issue details/rest/api/3/issue/{issueIdOrKey}/comment- list issue comments/rest/api/3/issue/{issueIdOrKey}/worklog- list issue worklogs/rest/api/3/issue/{issueIdOrKey}/transitions- get available transitions/rest/api/3/user/search- search users (usequeryparam)/rest/api/3/status- list all statuses/rest/api/3/issuetype- list issue types/rest/api/3/priority- list priorities
JQ examples: issues[*].key, issues[0], issues[*].{key: key, summary: fields.summary}
Example JQL queries: project=PROJ, assignee=currentUser(), status="In Progress", created >= -7d
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Inputs: path (required), queryParams, jq, outputFormat.
jira_patchJira PATCH RequestA
Partially update Jira resources. Returns TOON format by default.
IMPORTANT - Cost Optimization: Use jq param to filter response fields.
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Update issue fields:
/rest/api/3/issue/{issueIdOrKey}body:{"fields": {"summary": "Updated title"}}(only updates specified fields)Update comment:
/rest/api/3/issue/{issueIdOrKey}/comment/{commentId}body:{"body": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Updated comment"}]}]}}Update worklog:
/rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId}body:{"timeSpentSeconds": 7200}
Note: PATCH only updates the fields you specify, leaving others unchanged.
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Inputs: path (required), body (required), queryParams, jq, +1 more.
jira_postJira POST RequestA
Create Jira resources. Returns TOON format by default (token-efficient).
IMPORTANT - Cost Optimization:
Use
jqparam to extract only needed fields from response (e.g.,jq: "{key: key, id: id}")Unfiltered responses include all metadata and are expensive!
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Create issue:
/rest/api/3/issuebody:{"fields": {"project": {"key": "PROJ"}, "summary": "Issue title", "issuetype": {"name": "Task"}, "description": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Description"}]}]}}}Add comment:
/rest/api/3/issue/{issueIdOrKey}/commentbody:{"body": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Comment text"}]}]}}Add worklog:
/rest/api/3/issue/{issueIdOrKey}/worklogbody:{"timeSpentSeconds": 3600, "comment": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "Work done"}]}]}}Transition issue:
/rest/api/3/issue/{issueIdOrKey}/transitionsbody:{"transition": {"id": "31"}}Add attachment:
/rest/api/3/issue/{issueIdOrKey}/attachmentsNote: Requires multipart form data (complex - use Jira UI for attachments)
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Inputs: path (required), body (required), queryParams, jq, +1 more.
jira_putJira PUT RequestA
Replace Jira resources (full update). Returns TOON format by default.
IMPORTANT - Cost Optimization: Use jq param to extract only needed fields from response
Output format: TOON (default) or JSON (outputFormat: "json")
Common operations:
Update issue (full):
/rest/api/3/issue/{issueIdOrKey}body:{"fields": {"summary": "New title", "description": {...}, "assignee": {"accountId": "..."}}}Update project:
/rest/api/3/project/{projectIdOrKey}body:{"name": "New Project Name", "description": "Updated description"}Set issue property:
/rest/api/3/issue/{issueIdOrKey}/properties/{propertyKey}body:{"value": "property value"}
Note: PUT replaces the entire resource. For partial updates, prefer PATCH.
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
Inputs: path (required), body (required), queryParams, jq, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool is clearly distinguished by HTTP method (health_check, jira_delete, jira_get, jira_patch, jira_post, jira_put), with no overlap in purpose. The health_check serves a distinct configuration verification role, while the others map cleanly to CRUD operations on Jira resources.
All tools follow a consistent naming pattern: 'jira_' prefix followed by the HTTP method (delete, get, patch, post, put), except health_check which still fits the descriptive style. This creates a predictable and readable set where each tool's function is immediately apparent from its name.
Six tools is reasonable for a Jira server, covering core HTTP methods plus health monitoring. While slightly lean compared to more specialized Jira servers, it provides essential CRUD coverage. The count feels purposeful rather than excessive or insufficient for the domain.
The tools provide comprehensive CRUD coverage for Jira resources through HTTP method abstraction, with health_check adding operational monitoring. Minor gaps exist (e.g., no dedicated search tool beyond jira_get with JQL), but agents can accomplish most Jira workflows through the provided HTTP method tools and path parameters.
Related MCP Connectors
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
Manage Jensi projects, tasks, sprints and the AI suggestion inbox from your AI assistant.
Task manager your agent can fully operate: boards, tasks, sprints, roles, worklogs, day planner.
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.