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
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. Exposed over MCP by the atlassian jira mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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.
Everything the assistant can do here goes through one of these:
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)Requirements — The Requirements tool exposed by this serverArchitecture — This server follows the 5-layer MCP architecture: 1. CLI Layer - Human interface using Commander.js 2. Tools Layer - AI interface with ZodDebugging — Enable debug logging by setting the DEBUG environment variable:Installation goes through your MCP client rather than a global install: point it at @aashari/mcp-server-atlassian-jira on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 4 environment variables: ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN, DEBUG. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Atlassian Jira's toolset — jira_get, jira_post, jira_put and 5 more — is a fair guide to whether it matches your workflow. It is maintained by aashari; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Atlassian Jira's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| 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) |
| Requirements | The Requirements tool exposed by this server. |
| Architecture | This server follows the 5-layer MCP architecture: 1. **CLI Layer** - Human interface using Commander.js 2. **Tools Layer** - AI interface with Zod validation 3. **Controllers Layer** - Business logic and orchestration 4. |
| Debugging | Enable debug logging by setting the DEBUG environment variable: |
{
"mcpServers": {
"server-atlassian-jira": {
"command": "npx",
"args": ["-y", "@aashari/mcp-server-atlassian-jira"],
"env": {
"ATLASSIAN_SITE_NAME": "your-value",
"ATLASSIAN_USER_EMAIL": "your-value",
"ATLASSIAN_API_TOKEN": "your-value",
"DEBUG": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ATLASSIAN_SITE_NAME | Configuration value read at startup. | Optional |
| ATLASSIAN_USER_EMAIL | Configuration value read at startup. | Optional |
| ATLASSIAN_API_TOKEN | Credential the server authenticates with. | Yes |
| DEBUG | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.