Jira MCP server with scoped API tokens via api.atlassian.com gateway
MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Jira MCP server with scoped API tokens via api.atlassian.com gateway.
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 MCP is connected, these are the calls the assistant has available:
read — jira-work — read issues, search, comments, projectswrite — jira-work — create/update/delete issues, add commentsjira_get_issue — Get issue by key. Pass includeCustomFields: true to return all custom fieldsjira_search — Search issues via JQL with paginationjira_list_comments — List comments on an issuejira_list_projects — List accessible projectsjira_get_project — Get project details by keyjira_list_link_types — List available issue link typesjira_list_fields — List all fields (system + custom) — discover customfield_* IDsjira_list_attachments — List attachments on an issue with filename, size, MIME type, and download URLjira_get_transitions — Get available transitions for an issue with required screen fields expandedjira_create_issue — Create an issue (task, bug, story, epic). Supports custom fieldsYou will need 5 environment variables: JIRA_INSTANCE, JIRA_USER_EMAIL, JIRA_API_TOKEN, JIRA_SCOPES, JIRA_CLOUD_ID. 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.
mcp-jira-scoped on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — read, write, jira_get_issue and 11 more — is a fair guide to whether it matches your workflow. It is maintained by deepwired; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| read | jira-work — read issues, search, comments, projects |
| write | jira-work — create/update/delete issues, add comments |
| 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_project | Get project details by key |
| jira_list_link_types | List available issue link types |
| jira_list_fields | List all fields (system + custom) — discover customfield_* IDs |
| jira_list_attachments | List attachments on an issue with filename, size, MIME type, and download URL |
| jira_get_transitions | Get available transitions for an issue with required screen fields expanded |
| jira_create_issue | Create an issue (task, bug, story, epic). Supports custom fields |
| jira_update_issue | Update fields on an issue. Supports custom fields |
| jira_add_comment | Add a comment (plain text auto-converted to ADF) |
{
"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"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| JIRA_INSTANCE | Configuration value read at startup. | Optional |
| JIRA_USER_EMAIL | Configuration value read at startup. | Optional |
| JIRA_API_TOKEN | Credential the server authenticates with. | Yes |
| JIRA_SCOPES | Configuration value read at startup. | Optional |
| JIRA_CLOUD_ID | 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.