Atlassian Jira MCP Server
Jira projects, issues, and workflow management for your AI assistant.
Data last scanned today · Reviewed today
Overview
This TypeScript-based MCP server facilitates direct integration between AI assistants and Atlassian Jira environments. It allows users to query project data, manage issue comments, and perform CRUD operations on Jira tickets using natural language prompts. Developers, project managers, and QA engineers can leverage this bridge to automate tracking tasks, retrieve issue details like status or priority, and sync team progress without manually navigating the Jira web interface.
Our verdict
With a security score of 21/100, this server is classified as high-risk and is intended for use with caution. The tool lacks a defined open-source license, which creates ambiguity regarding legal usage and distribution. Furthermore, because it is a community-maintained project rather than an official Atlassian integration, users should be aware of the potential for unvetted security practices and the lack of official support channels.
- Supports direct creation and updates of Jira issues
- Provides built-in JMESPath filtering for issue queries
- Small dependency footprint with only 9 direct packages
- No license detected, creating unclear legal usage terms
- Not maintained by the official Atlassian vendor
- Inactive repository with no updates for over 140 days
Setup
{
"mcpServers": {
"mcp-server-atlassian-jira": {
"args": [
"-y",
"@aashari/mcp-server-atlassian-jira"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| jira_get | GET any Jira API endpoint (read data) | low |
| jira_post | POST to any endpoint (create resources) | medium |
| jira_put | PUT to any endpoint (replace resources) | medium |
| jira_patch | PATCH any endpoint (partial updates) | medium |
| jira_delete | DELETE any endpoint (remove resources) | high |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What authentication is required to use this MCP server?
You need to provide your Jira site name, the email address associated with your account, and a Jira API token generated from the Atlassian security settings page.
›How can I change the data format from TOON to standard JSON?
You can switch the output format by adding the --output-format json flag to your CLI commands or by setting outputFormat to "json" in your MCP tool calls.
›Does the server support global configuration?
Yes, you can configure the server system-wide by creating a configuration file at ~/.mcp/configs.json.
›What tools are provided for interacting with Jira?
The server provides five generic tools, which are jira_get, jira_post, jira_put, jira_patch, and jira_delete, allowing access to any Jira API endpoint.
›How do I filter the output returned by the Jira tools?
All tools support optional JMESPath (jq) filtering, which allows you to extract specific data fields from the API responses.
Badge
Maintain this server? Add the live badge to your README.