
Research
/Security News
Bitwarden CLI Compromised in Ongoing Checkmarx Supply Chain Campaign
Bitwarden CLI 2026.4.0 was compromised in the Checkmarx supply chain campaign after attackers abused a GitHub Action in Bitwarden’s CI/CD pipeline.
@aashari/mcp-server-atlassian-jira
Advanced tools
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 tracki
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.
Get up and running in 2 minutes:
Generate a Jira API Token:
# 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}"
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.
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.
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".
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) |
Projects:
/rest/api/3/project/search - List all projects/rest/api/3/project/{projectKeyOrId} - Get project detailsIssues:
/rest/api/3/search/jql - Search issues with JQL (use jql query param)/rest/api/3/issue/{issueIdOrKey} - Get issue details/rest/api/3/issue - Create issue (POST)/rest/api/3/issue/{issueIdOrKey}/transitions - Get/perform transitionsComments:
/rest/api/3/issue/{issueIdOrKey}/comment - List/add comments/rest/api/3/issue/{issueIdOrKey}/comment/{commentId} - Get/update/delete commentWorklogs:
/rest/api/3/issue/{issueIdOrKey}/worklog - List/add worklogs/rest/api/3/issue/{issueIdOrKey}/worklog/{worklogId} - Get/update/delete worklogUsers & 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 prioritiesAll 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}"
Ask your AI assistant:
Ask your AI assistant:
Ask your AI assistant:
Ask your AI assistant:
The CLI mirrors the MCP tools for direct terminal access:
# GET request
npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/project/search"
# GET with query parameters
npx -y @aashari/mcp-server-atlassian-jira get \
--path "/rest/api/3/search/jql" \
--query-params '{"jql": "project=DEV AND status=\"In Progress\"", "maxResults": "10"}'
# POST request (create an issue)
npx -y @aashari/mcp-server-atlassian-jira post \
--path "/rest/api/3/issue" \
--body '{"fields": {"project": {"key": "DEV"}, "summary": "New issue title", "issuetype": {"name": "Task"}}}'
# POST request (add a comment)
npx -y @aashari/mcp-server-atlassian-jira post \
--path "/rest/api/3/issue/PROJ-123/comment" \
--body '{"body": {"type": "doc", "version": 1, "content": [{"type": "paragraph", "content": [{"type": "text", "text": "My comment"}]}]}}'
# PUT request (update issue - full replacement)
npx -y @aashari/mcp-server-atlassian-jira put \
--path "/rest/api/3/issue/PROJ-123" \
--body '{"fields": {"summary": "Updated title"}}'
# DELETE request
npx -y @aashari/mcp-server-atlassian-jira delete \
--path "/rest/api/3/issue/PROJ-123/comment/12345"
Check your API Token permissions:
Verify your site name format:
https://mycompany.atlassian.netmycompanyTest your credentials:
npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/myself"
Check the API path:
DEV) not project namesDEV-123)Verify access permissions:
Try different search terms:
Check JQL syntax:
~/.claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonIf you're still having issues:
Your Atlassian account needs:
Currently, this tool only supports Jira Cloud. Jira Server/Data Center support may be added in future versions.
Your site name is the first part of your Jira URL:
https://mycompany.atlassian.net -> Site name: mycompanyhttps://acme-corp.atlassian.net -> Site name: acme-corpAny AI assistant that supports the Model Context Protocol (MCP):
Yes! This tool:
Yes! Use JQL queries for cross-project searches. For example:
npx -y @aashari/mcp-server-atlassian-jira get \
--path "/rest/api/3/search/jql" \
--query-params '{"jql": "assignee=currentUser() AND status=\"In Progress\""}'
Version 3.0 replaces 8+ specific tools with 5 generic HTTP method tools. If you're upgrading from v2.x:
Before (v2.x):
jira_ls_projects, jira_get_project, jira_ls_issues, jira_get_issue,
jira_create_issue, jira_ls_comments, jira_add_comment, jira_ls_statuses, ...
After (v3.0):
jira_get, jira_post, jira_put, jira_patch, jira_delete
Migration examples:
jira_ls_projects -> jira_get with path /rest/api/3/project/searchjira_get_project -> jira_get with path /rest/api/3/project/{key}jira_get_issue -> jira_get with path /rest/api/3/issue/{key}jira_create_issue -> jira_post with path /rest/api/3/issuejira_add_comment -> jira_post with path /rest/api/3/issue/{key}/commentjira_ls_statuses -> jira_get with path /rest/api/3/statusNeed help? Here's how to get assistance:
Made with care for teams who want to bring AI into their project management workflow.
FAQs
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 tracki
The npm package @aashari/mcp-server-atlassian-jira receives a total of 5,477 weekly downloads. As such, @aashari/mcp-server-atlassian-jira popularity was classified as popular.
We found that @aashari/mcp-server-atlassian-jira demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
Bitwarden CLI 2026.4.0 was compromised in the Checkmarx supply chain campaign after attackers abused a GitHub Action in Bitwarden’s CI/CD pipeline.

Research
/Security News
Docker and Socket have uncovered malicious Checkmarx KICS images and suspicious code extension releases in a broader supply chain compromise.

Product
Stay on top of alert changes with filtered subscriptions, batched summaries, and notification routing built for triage.