Jira MCP server with scoped API tokens via api.atlassian.com gateway
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.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| 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 |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
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.