Mcp Jira Scoped
Query and update Jira issues from your agent using least-privilege scoped API tokens via Atlassian’s gateway.
Overview
mcp-jira-scoped is a Build-phase MCP server that talks to Jira Cloud via scoped API tokens on the Atlassian gateway.
What is this MCP server?
- Jira access through api.atlassian.com with scoped API tokens (read/write/jira-user/me scopes)
- Required env: JIRA_INSTANCE, JIRA_USER_EMAIL, JIRA_API_TOKEN; optional JIRA_SCOPES and JIRA_CLOUD_ID
- npx-friendly npm package mcp-jira-scoped v1.0.0 stdio
- Defaults scopes to read:jira-work when JIRA_SCOPES unset
- Cloud ID auto-fetch when JIRA_CLOUD_ID omitted
- Version 1.0.0
- Documented scope values: read:jira-work, write:jira-work, read:jira-user, read:me
- Default scope read:jira-work when JIRA_SCOPES unset
Community signal: 2 GitHub stars.
What problem does it solve?
Hooking Jira to an agent often means over-broad tokens or manual copy-paste of ticket context into every task.
Who is it for?
Indie builders on Jira Cloud who want agent issue lookup and updates with token scopes they can revoke and audit.
Skip if: Self-hosted Jira without cloud gateway support, or teams that refuse cloud API tokens in local agent configs.
What do I get? / Deliverables
You register scoped credentials once and the agent can read or update Jira work within the limits you set in JIRA_SCOPES.
- Agent-driven Jira issue search and updates within declared scopes
- Configurable permission boundary via JIRA_SCOPES
- Optional cloud ID resolution for tenant routing
Recommended MCP Servers
Journey fit
Build is where issue trackers tie commits to tickets; this server is an integration layer during implementation and coordination. Integrations subphase matches an external Jira bridge with explicit env-based auth—not a standalone planning methodology.
How it compares
Scoped Jira MCP bridge, not a sprint planning skill or standalone PM product.
Common Questions / FAQ
Who is mcp-jira-scoped for?
Developers using Jira Cloud who want Claude Code or similar agents to work tickets with narrowly scoped Atlassian API tokens.
When should I use mcp-jira-scoped?
Use it during Build when you file bugs, link branches to issues, or transition cards while coding—with permissions capped via JIRA_SCOPES.
How do I add mcp-jira-scoped to my agent?
Create a scoped token at id.atlassian.com, set JIRA_INSTANCE, JIRA_USER_EMAIL, and JIRA_API_TOKEN, optionally JIRA_SCOPES and JIRA_CLOUD_ID, then run mcp-jira-scoped via npx as a stdio MCP server.