mcp-jira

[](https://www.npmjs.com/package/mcp-jira-scoped) [](LICENSE) [](https://nodejs.org) [](https://www.typescriptlang.org)

The only MCP server for Jira that works with Atlassian's scoped API tokens.

Every other Jira MCP server uses classic (unscoped) API tokens with basic auth against yoursite.atlassian.net. Atlassian is deprecating those. This server uses scoped tokens with the modern api.atlassian.com gateway — the way Atlassian intends these tokens to be used.

Once connected, you can ask your AI assistant things like:

• *"What's the status of PROJ-1234?"*
• *"Search for all open bugs assigned to me in the BACKEND project"*
• *"Create a story in PROJ for the database migration, priority P2, under epic PROJ-100"*
• *"Move PROJ-1234 to In Progress"*
• *"Add a comment to PROJ-1234 saying the fix is deployed to staging"*
• *"Link PROJ-1234 as blocking PROJ-5678"*
• *"Find all issues with 'auth' in the summary updated this week"*

| | mcp-jira-scoped | Other Jira MCP servers | |---|---|---| | Token type | Scoped (modern, ATATT prefix) | Classic (being deprecated) | | Auth gateway | api.atlassian.com | yoursite.atlassian.net | | Scope enforcement | Server-side, before every API call | None — relies on AI self-restraint | | Default mode | Read-only (write must be explicitly granted) | Full access | | Delete safety | Requires confirm: true parameter | No guard |

1. Go to Atlassian API Tokens
2. Click "Create API token with scopes"
3. Grant the scopes you need:

• read:jira-work — read issues,