Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"jira": {
"env": {
"JIRA_SCOPES": "read:jira-work,write:jira-work",
"JIRA_INSTANCE": "yourcompany",
"JIRA_API_TOKEN": "<your-scoped-token>",
"JIRA_USER_EMAIL": "you@yourcompany.com"
},
"args": [
"-y",
"mcp-jira-scoped"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The only MCP server for Jira that works with Atlassian's scoped API tokens.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-jira-scoped' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-jira-scoped against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / developer-tools
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
Read, write, and manage files on the local filesystem
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
MCP Security Weekly
Get CVE alerts and security updates for io.github.deepwired/mcp-jira-scoped and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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:
| 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 |
read:jira-work — read issues, search, comments, projectswrite:jira-work — create/update/delete issues, add commentsread:jira-user — look up usersread:me — read your own profileAdd to your .mcp.json:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "mcp-jira-scoped"],
"env": {
"JIRA_INSTANCE": "yourcompany",
"JIRA_USER_EMAIL": "you@yourcompany.com",
"JIRA_API_TOKEN": "<your-scoped-token>",
"JIRA_SCOPES": "read:jira-work,write:jira-work"
}
}
}
}
Add the same config to Cursor's MCP settings (Settings > MCP Servers).
Add to .vscode/mcp.json:
{
"servers": {
"jira": {
"command": "npx",
"args": ["-y", "mcp-jira-scoped"],
"env": {
"JIRA_INSTANCE": "yourcompany",
"JIRA_USER_EMAIL": "you@yourcompany.com",
"JIRA_API_TOKEN": "<your-scoped-token>",
"JIRA_SCOPES": "read:jira-work,write:jira-work"
}
}
}
}
| Env Var | Required | Description |
|---|---|---|
JIRA_INSTANCE | Yes | Instance name (e.g. mycompany for mycompany.atlassian.net) |
JIRA_API_TOKEN | Yes | Scoped API token (ATATT... prefix) |
JIRA_USER_EMAIL | Yes | Email associated with the token |
JIRA_SCOPES | No | Comma-separated scopes. Defaults to read:jira-work (read-only) |
JIRA_CLOUD_ID | No | Atlassian Cloud ID. Auto-fetched if not set. Find it at https://yoursite.atlassian.net/_edge/tenant_info |
read:jira-work)| Tool | Description |
|---|---|
jira_get_issue | Get issue by key. Pass includeCustomFields: true to return all custom fields |
jira_search | Search issues via JQL with pagination |
jira_list_comments | List comments on an issue |
jira_list_projects | List accessible projects |
| `jira_get |