Atlassian Jira MCP Server

by aashari

72 stars
617 downloads
Not rated
GitHub

About

Node.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.

Details

Author
aashari
GitHub stars
72
Downloads
617
Categories
Productivity, Project Management, Developer Tools, AI

- Five generic CRUD tools for any Jira REST API endpoint
- TOON format reduces token usage by 30–60%
- JMESPath filtering to extract specific fields
- Automatic response truncation for large payloads (>40k characters)
- CLI commands mirror all MCP tools for direct terminal use
- Optional JSON output via --output-format json

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Atlassian Jira MCP Server
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Generate a Jira API token, set environment variables (ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN), then either use the CLI directly (npx -y @aashari/mcp-server-atlassian-jira get ...) or configure your AI assistant (e.g., Claude Desktop's claude_desktop_config.json) to use the MCP server with STDIO transport. The server provides five generic tools: jira_get, jira_post, jira_put, jira_patch, and jira_delete.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "atlassian jira mcp server": {
            "mcp-server-atlassian-jira": {
                "command": "npx",
                "args": [
                    "-y",
                    "@aashari/mcp-server-atlassian-jira",
                    "get",
                    "--path",
                    "/rest/api/3/project/search"
                ]
            }
        }
    }
}

McpServers

{
    "mcp-server-atlassian-jira": {
        "command": "npx",
        "args": [
            "-y",
            "@aashari/mcp-server-atlassian-jira",
            "get",
            "--path",
            "/rest/api/3/project/search"
        ]
    }
}

Connect AI to Your Jira Projects

Transform how you manage and track your work by connecting Claude, Cursor AI, and other AI assistants directly to your Jira projects, issues, and workflows. Get instant project insights, streamline issue management, and enhance your team collaboration.

NPM Version

What You Can Do

- Ask AI about your projects: "What are the active issues in the DEV project?"
- Get issue insights: "Show me details about PROJ-123 including comments"
- Track project progress: "List all high priority issues assigned to me"
- Manage issue comments: "Add a comment to PROJ-456 about the test results"
- Search across projects: "Find all bugs in progress across my projects"
- Create and update issues: "Create a new bug in the MOBILE project"

Perfect For

- Developers who need quick access to issue details and development context
- Project Managers tracking progress, priorities, and team assignments
- Scrum Masters managing sprints and workflow states
- Team Leads monitoring project health and issue resolution
- QA Engineers tracking bugs and testing status
- Anyone who wants to interact with Jira using natural language

Quick Start

Get up and running in 2 minutes:

1. Get Your Jira Credentials

Generate a Jira API Token:
1. Go to Atlassian API Tokens
2. Click Create API token
3. Give it a name like "AI Assistant"
4. Copy the generated token immediately (you won't see it again!)

2. Try It Instantly

# Set your credentials
export ATLASSIAN_SITE_NAME="your-company"  # for your-company.atlassian.net
export ATLASSIAN_USER_EMAIL="your.email@company.com"
export ATLASSIAN_API_TOKEN="your_api_token"

List your Jira projects

npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/project/search"

Get details about a specific project

npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/project/DEV"

Get an issue with JMESPath filtering

npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/issue/PROJ-123" --jq "{key: key, summary: fields.summary, status: fields.status.name}"

Connect to AI Assistants

For Claude Desktop Users

Add this to your Claude configuration file (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "@aashari/mcp-server-atlassian-jira"],
      "env": {
        "ATLASSIAN_SITE_NAME": "your-company",
        "ATLASSIAN_USER_EMAIL": "your.email@company.com",
        "ATLASSIAN_API_TOKEN": "your_api_token"
      }
    }
  }
}

Restart Claude Desktop, and you'll see the jira server in the status bar.

For Other AI Assistants

Most AI assistants support MCP. Install the server globally:

npm install -g @aashari/mcp-server-atlassian-jira

Then configure your AI assistant to use the MCP server with STDIO transport.

Alternative: Configuration File

Create ~/.mcp/configs.json for system-wide configuration:

{
  "jira": {
    "environments": {
      "ATLASSIAN_SITE_NAME": "your-company",
      "ATLASSIAN_USER_EMAIL": "your.email@company.com",
      "ATLASSIAN_API_TOKEN": "your_api_token"
    }
  }
}

Alternative config keys: The system also accepts "atlassian-jira", "@aashari/mcp-server-atlassian-jira", or "mcp-server-atlassian-jira" instead of "jira".

Available Tools

This MCP server provides 5 generic tools that can access any Jira API endpoint:

| Tool | Description |
|------|-------------|
| jira_get | GET any Jira API endpoint (read data) |
| jira_post | POST to any endpoint (create resources) |
| jira_put | PUT to any endpoint (replace resources) |
| jira_patch | PATCH any endpoint (partial updates) |
| jira_delete | DELETE any endpoint (remove resources) |

Common API Paths

Projects:
- /rest/api/3/project/search - List all projects (paginated, recommended)
- /rest/api/3/project - List all projects (non-paginated, legacy)
- /rest/api/3/project/{projectKeyOrId} - Get project details

Issues:
- /rest/api/3/search/jql - Search issues with JQL (use jql query param). IMPORTANT: /rest/api/3/search is deprecated!
- /rest/api/3/issue/{issueIdOrKey} - Get issue details
- /rest/api/3/issue - Create issue (POST)
- /rest/api/3/issue/{issueIdOrKey}/transitions - Get/perform transitions

Comments:
- /rest/api/3/issue/{issueIdOrKey}/comment - List/add comments
- /rest/api/3/issue/{issueIdOrKey}/comment/{commentId} - Get/update/delete comment

Worklogs:
- /rest/api/3/issue/{issueIdOrKey}/worklog - List/add worklogs
- /rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId} - Get/update/delete worklog

Users & Statuses:
- /rest/api/3/myself - Get current user
- /rest/api/3/user/search - Search users (use query param)
- /rest/api/3/status - List all statuses
- /rest/api/3/issuetype - List issue types
- /rest/api/3/priority - List priorities

TOON Output Format

By default, all responses use TOON (Token-Oriented Object Notation) format, which reduces token usage by 30-60% compared to JSON. TOON uses tabular arrays and minimal syntax, making it ideal for AI consumption.

To use JSON instead: Add --output-format json to CLI commands or set outputFormat: "json" in MCP tool calls.

Example TOON vs JSON:

TOON: key|summary|status
PROJ-1|First issue|Open
PROJ-2|Second issue|Done

JSON: [{"key":"PROJ-1","summary":"First issue","status":"Open"},
{"key":"PROJ-2","summary":"Second issue","status":"Done"}]

JMESPath Filtering

All tools support optional JMESPath (jq) filtering to extract specific data:

# Get just project names and keys
npx -y @aashari/mcp-server-atlassian-jira get \
  --path "/rest/api/3/project/search" \
  --jq "values[].{key: key, name: name}"

Get issue key and summary

npx -y @aashari/mcp-server-atlassian-jira get \ --path "/rest/api/3/issue/PROJ-123" \ --jq "{key: key, summary: fields.summary, status: fields.status.name}"

Response Truncation and Raw Logs

For large API responses (>40k characters ≈ 10k tokens), responses are automatically truncated with guidance. The complete raw response is saved to /tmp/mcp/mcp-server-atlassian-jira/<timestamp>-<random>.txt for reference.

When truncated, you'll see:
- A truncation notice with the raw file path
- Suggestions to refine your query with better filters
- Percentage of data shown vs total size

Real-World Examples

Explore Your Projects

Ask your AI assistant:
- "List all projects I have access to"
- "Show me details about the DEV project"
- "What projects contain the word 'Platform'?"

Search and Track Issues

Ask your AI assistant:
- "Find all high priority issues in the DEV project"
- "Show me issues assigned to me that are in progress"
- "Search for bugs reported in the last week"
- "List all open issues for the mobile team"

Manage Issue Details

Ask your AI assistant:
- "Get full details about issue PROJ-456 including comments"
- "What's the current status and assignee of PROJ-123?"
- "Display all comments on the authentication bug"

Issue Communication

Ask your AI assistant:
- "Add a comment to PROJ-456: 'Code review completed, ready for testing'"
- "Comment on the login issue that it's been deployed to staging"

CLI Commands

The CLI mirrors the MCP tools for direct terminal access:

```bash

GET request (returns TOON format by default)


npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/project/search"

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.