Jira MCP server

Last verified: 2026-09

Jira issues and JQL search.

Community Chat, mail & docs Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code

What it does

Generic HTTP verbs against the Jira REST API (jira_get/post/put/patch/delete). Powerful and easy to misuse — it is not a curated 'create issue' wrapper, it is the API.

It sits in Chat, mail & docs: These servers act as the bot or the integration you install.

Good for

jira_get /rest/api/3/myself then one project — prove the token works.
JQL via the REST path you already use in the UI.
Create an issue only with a bot user, not your admin account.
Leave jira_delete unused. This wrapper is the whole API.

Tools

jira_get — Read any Jira REST path.
jira_post / jira_put / jira_patch — Create or change resources.
jira_delete — Delete.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira"
      ],
      "env": {
        "ATLASSIAN_SITE": "yourhost.atlassian.net",
        "ATLASSIAN_EMAIL": "[email protected]",
        "ATLASSIAN_API_TOKEN": "..."
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y @aashari/mcp-server-atlassian-jira

Secrets it wants: ATLASSIAN_SITE, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN

Source repo →

How to get started

Use an Atlassian API token. Site = yourhost.atlassian.net.
Start by jira_get on /rest/api/3/myself and one project.
Do not enable delete until you need it. Prefer a dedicated bot user.

Access risk

Five verbs = the whole Jira API. A token with admin can change workflows and delete issues.

When to skip it

Skip it for Linear or GitHub issues. Skip it if you wanted a safe create-issue-only server.

Instead: Linear, GitHub, Confluence.

Chat, mail & docsLinearIssues, projects, and cycles in Linear. OfficialGitHubRepos, issues, PRs, and file contents on GitHub. Chat, mail & docsConfluenceRead Confluence pages.

Vs alternatives

Server	Official?	Needs a secret?	Best for
Jira	No	Yes	Jira issues and JQL search.
Linear	No	Yes	Issues, projects, and cycles in Linear.
GitHub	Yes	Yes	Repos, issues, PRs, and file contents on GitHub.
Confluence	No	Yes	Read Confluence pages.

More in Chat, mail & docs

OfficialGoogle MapsGeocode and place search via Google Maps. OfficialSlackRead channels and post messages. Chat, mail & docsAsanaTasks and projects in Asana. Chat, mail & docsConfluenceRead Confluence pages.

All 18 in this category →

FAQ

Why generic GET/POST instead of create_issue?

This community server is five HTTP verbs against any Jira path. Powerful and easy to misuse. If you wanted a safe wrapper, this is not it.

Cloud or Server?

ATLASSIAN_SITE is yourhost.atlassian.net plus email + API token. Confirm Server/DC support in the repo if you are not on Cloud.

Jira or Linear?

Match the tracker. Same Atlassian token is often reused for Confluence — that widens blast radius.

Admin token?

No. A token that can change workflows can wreck the project.