Skip to main content
Glama

Jira MCP Server

A Model Context Protocol (MCP) server for Jira Cloud. It exposes issue, project, board, sprint, search, comment, worklog, link, version, attachment and property operations as MCP tools, backed directly by the Jira Cloud REST API (v3) and Agile API (1.0).

This project is not affiliated with, endorsed by, or sponsored by Atlassian.

Table of Contents

Related MCP server: JIRA MCP Server

Overview

  • Auth: Jira Cloud API token (email + token, Basic Auth) — no OAuth redirect flow needed.

  • HTTP client: Node's native fetch/FormData — no extra HTTP dependency.

  • Runtime deps: just @modelcontextprotocol/sdk and zod.

  • Destructive/admin tools are off by default: deleteJiraIssue, deleteJiraComment, deleteJiraIssueAttachment, createJiraProject, updateJiraProject only register when you explicitly opt in via env vars (see below).

Prerequisites

Setup

  1. Clone/copy this project, then install dependencies:

    npm install
    npm run build
  2. Or, once published, install as a dependency of your own project:

npm i @automate-io/jira-mcp-server@latest


## Configuration

The server reads its Jira connection from environment variables — set these in your MCP
client's server config, never commit them to source control.

| Variable | Required | Description |
| --- | --- | --- |
| `JIRA_URL` | Yes | Your site, e.g. `https://your-domain.atlassian.net` |
| `JIRA_USERNAME` | Yes | Account email used to generate the API token |
| `JIRA_TOKEN` | Yes | API token from id.atlassian.com |
| `JIRA_ENABLE_DELETE` | No | Set to `true` to register `deleteJiraIssue`/`deleteJiraComment`/`deleteJiraIssueAttachment` |
| `JIRA_ENABLE_MANAGE` | No | Set to `true` to register `createJiraProject`/`updateJiraProject` |

Example `.vscode/mcp.json` (also included in this repo, using prompted inputs so the token
isn't hardcoded):

```json
{
"servers": {
 "jira-mcp": {
   "type": "stdio",
   "command": "node",
   "args": ["node_modules/@automate-io/jira-mcp-server/dist/server.js"],
   "cwd": "${workspaceFolder}",
   "env": {
     "JIRA_URL": "${input:jiraBaseUrl}",
     "JIRA_USERNAME": "${input:jiraEmail}",
     "JIRA_TOKEN": "${input:jiraApiToken}"
   }
 }
},
"inputs": [
 { "id": "jiraBaseUrl", "type": "promptString", "description": "Jira Cloud site URL" },
 { "id": "jiraEmail", "type": "promptString", "description": "Jira account email" },
 { "id": "jiraApiToken", "type": "promptString", "description": "Jira API token", "password": true }
]
}

Tool catalogue

Grouped by file under src/tools/. 41 tools by default, 46 with delete/manage enabled.

File

Tools

issues.ts

getJiraIssue, createJiraIssue, editJiraIssue, listJiraIssueTransitions, transitionJiraIssue, listJiraIssueChangelogs, watchJiraIssue, deleteJiraIssue

comments.ts

listJiraIssueComments, addOrEditJiraIssueComment, deleteJiraComment

worklogs.ts

listJiraIssueWorklogs, addOrEditJiraIssueWorklog

links.ts

listJiraIssueLinkTypes, createJiraIssueLink, listJiraIssueRemoteIssueLinks

search.ts

searchJiraIssuesUsingJql

users.ts

getJiraCurrentUser, getJiraUser, lookupJiraAccountId, findJiraIssueAssignableUsers

projects.ts

listJiraProjects, listJiraProjectIssueTypesMetadata, getJiraIssueTypeMetaWithFields, listJiraStatuses, listJiraProjectComponents, createJiraProject, updateJiraProject

versions.ts

getJiraProjectVersions, manageJiraProjectVersion, getJiraProjectVersionRelatedWork, manageJiraProjectVersionRelatedWork

boards.ts

listJiraBoards, getJiraBoardConfig, getJiraBoardIssueData, createJiraBoard

sprints.ts

listJiraBoardSprints, getJiraBoardSprintData, manageJiraSprint

filtersAndDashboards.ts

listJiraFilters, listJiraDashboards

properties.ts

getJiraEntityProperty, editJiraEntityProperty

attachments.ts

uploadAttachmentToJiraIssue, downloadJiraIssueAttachment, deleteJiraIssueAttachment

Italicised tools require the matching JIRA_ENABLE_* flag.

Design notes

  • src/utilities/jira-client.ts is the single HTTP entry point (jiraRequest). It preserves the real HTTP status code on every response (including errors), parses the body by content-type instead of assuming JSON, and needs no manual context disposal since it's built on native fetch.

  • src/utilities/tool-helpers.ts provides safeHandler (shared try/catch) and toToolResult (maps a Jira response to MCP content with isError reflecting the real status), so each tool handler stays a few lines of Jira-specific logic instead of repeating boilerplate.

  • src/utilities/adf.ts converts plain text into the minimal Atlassian Document Format Jira Cloud's v3 API requires for rich-text fields (comments, descriptions, worklog comments).

  • searchJiraIssuesUsingJql uses the current token-paginated /rest/api/3/search/jql endpoint, since the older startAt-based /rest/api/3/search is deprecated.

  • Startup logs go to stderr, never stdout — stdout is reserved for the MCP JSON-RPC stream over the stdio transport, so anything else written there would corrupt it.

Troubleshooting

  • Server exits immediately with "Missing required environment variable": set JIRA_URL, JIRA_USERNAME, JIRA_TOKEN in your MCP client's server config.

  • 401/403 from Jira: regenerate your API token, and confirm JIRA_USERNAME matches the Atlassian account that owns the token.

  • A delete/manage tool doesn't show up: set JIRA_ENABLE_DELETE / JIRA_ENABLE_MANAGE to "true" in the server's env config.

Available Tools

41 tools
addOrEditJiraIssueCommentC

Add a comment, or edit an existing one.

Inputs: body (required), issueIdOrKey (required), commentId, visibilityType, +1 more.

addOrEditJiraIssueWorklogC

Log time on an work item, or edit an existing worklog.

Inputs: issueIdOrKey (required), comment, started, reduceBy, +5 more.

createJiraBoardB

Create a company-managed board (scrum or kanban) from an existing filter.

Inputs: name (required), type (required), filterId (required), projectKeyOrId.

createJiraIssueC

Create a new Jira work item.

Inputs: summary (required), projectKey (required), fields, update, +3 more.

downloadJiraIssueAttachmentB
Read-onlyIdempotent

Get a short-lived download URL for an attachment and a local command to save the file.

Inputs: attachmentId (required), savePath.

editJiraEntityPropertyB
Idempotent

Set a property in the key/value store on an work item, comment, worklog, dashboard item, or user.

Inputs: entityType (required), propertyKey (required), value, entityId, +3 more.

editJiraIssueC
Idempotent

Edit an existing work item; only fields editable on that work item can be set.

Inputs: issueIdOrKey (required), fields, update, notifyUsers.

findJiraIssueAssignableUsersC
Read-onlyIdempotent

Find users assignable to a Jira space or work item.

Inputs: query, maxResults, projectKey, issueIdOrKey.

getJiraBoardConfigB
Read-onlyIdempotent

A board's configuration: filter, column layout, and each column's mapped statuses.

Inputs: boardId (required).

getJiraBoardIssueDataC
Read-onlyIdempotent

The work items on a board, its backlog, or both, with optional count and JQL filtering.

Inputs: boardId (required), jql, fields, source, +2 more.

getJiraBoardSprintDataB
Read-onlyIdempotent

Resolve a board plus its sprint data in one call; defaults to the active sprint.

Inputs: boardId (required), sprintId, includeIssues.

getJiraCurrentUserB
Read-onlyIdempotent

Details for the current Jira user.

Inputs: no named parameters.

getJiraEntityPropertyB
Read-onlyIdempotent

Read a property from the key/value store on an work item, comment, worklog, dashboard item, or user.

Inputs: entityType (required), propertyKey (required), entityId, accountId, +2 more.

getJiraIssueC
Read-onlyIdempotent

Get a Jira work item by ID or key.

Inputs: issueIdOrKey (required), expand, fields, properties.

getJiraIssueTypeMetaWithFieldsB
Read-onlyIdempotent

Schema and field metadata for a specific work item type in a project, for creating work items with correct fields.

Inputs: issueTypeId (required), projectIdOrKey (required).

getJiraProjectVersionRelatedWorkC
Read-onlyIdempotent

Related work links (evidence) on a space version (release).

Inputs: versionId (required).

getJiraProjectVersionsC
Read-onlyIdempotent

A space's releases/versions, or a single version.

Inputs: startAt, versionId, maxResults, projectIdOrKey.

getJiraUserB
Read-onlyIdempotent

Retrieves a Jira user's profile by account ID.

Inputs: accountId (required).

listJiraBoardsC
Read-onlyIdempotent

Lists boards visible to the current user.

Inputs: name, type, startAt, maxResults, +1 more.

listJiraBoardSprintsB
Read-onlyIdempotent

Sprints from a board, optionally filtered to active, future, or closed.

Inputs: boardId (required), state, startAt, maxResults.

listJiraDashboardsC
Read-onlyIdempotent

Dashboards visible to the current user, for discovery and linking workflows.

Inputs: startAt, maxResults, dashboardName.

listJiraFiltersB
Read-onlyIdempotent

Search saved filters visible to the current user, returning IDs and JQL.

Inputs: startAt, accountId, filterName, maxResults.

listJiraIssueChangelogsB
Read-onlyIdempotent

An work item's field-change history, paginated oldest-first.

Inputs: issueIdOrKey (required), startAt, maxResults.

listJiraIssueCommentsC
Read-onlyIdempotent

Paginated comments for a Jira work item.

Inputs: issueIdOrKey (required), expand, orderBy, startAt, +1 more.

listJiraIssueLinkTypesC
Read-onlyIdempotent

Available work item link types in Jira.

Inputs: no named parameters.

listJiraIssueTransitionsC
Read-onlyIdempotent

Available workflow transitions for a Jira work item.

Inputs: issueIdOrKey (required).

listJiraIssueWorklogsB
Read-onlyIdempotent

Paginated worklogs (logged time) for a Jira work item.

Inputs: issueIdOrKey (required), startAt, maxResults, startedAfter, +1 more.

listJiraProjectComponentsC
Read-onlyIdempotent

Components in a space, with IDs, names, work item counts, and ownership details.

Inputs: projectIdOrKey (required).

listJiraProjectIssueTypesMetadataC
Read-onlyIdempotent

All work item types available in a Jira space.

Inputs: projectIdOrKey (required).

listJiraProjectsC
Read-onlyIdempotent

Get Jira spaces visible to the current user.

Inputs: query, startAt, maxResults.

listJiraStatusesB
Read-onlyIdempotent

List of statuses a Jira work item can be in.

Inputs: projectIdOrKey.

lookupJiraAccountIdB
Read-onlyIdempotent

Look up a Jira user account ID by display name or email.

Inputs: query (required), maxResults.

manageJiraProjectVersionC

Create, update, release, or archive a space version (release or fix version).

Inputs: operation (required), name, startDate, versionId, +3 more.

manageJiraProjectVersionRelatedWorkC

Create or update related work links on a space version.

Inputs: url (required), title (required), category (required), versionId (required), +1 more.

manageJiraSprintC

Create, populate, start, update, or close a sprint.

Inputs: operation (required), goal, name, endDate, +4 more.

searchJiraIssuesUsingJqlC
Read-onlyIdempotent

Search Jira work items using JQL.

Inputs: jql (required), expand, fields, maxResults, +1 more.

transitionJiraIssueB

Transition an work item to a new status, and/or assign it to a sprint or backlog.

Inputs: issueIdOrKey (required), transitionId (required), fields, comment.

uploadAttachmentToJiraIssueC

Attach a local file to an work item.

Inputs: filePath (required), issueIdOrKey (required), mimeType.

watchJiraIssueC
Idempotent

Watch or unwatch a work item.

Inputs: watch (required), issueIdOrKey (required), accountId.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists among board/sprint/issue-data retrieval tools (e.g., getJiraBoardIssueData vs searchJiraIssuesUsingJql) and version tools. Descriptions generally clarify boundaries well enough for an agent to select correctly.

    Naming Consistency4/5

    Names mostly follow a verb + Jira + noun pattern (e.g., getJiraIssue, listJiraProjects, createJiraIssue). Minor deviations like uploadAttachmentToJiraIssue and searchJiraIssuesUsingJql break the pattern slightly but remain readable and predictable.

    Tool Count2/5

    41 tools is heavy for a single MCP server and exceeds the 25+ threshold for being too many. Many operations could be consolidated (e.g., list/get/manage variants across issues, boards, and versions).

    Completeness3/5

    The surface covers broad read/write operations for issues, comments, worklogs, links, attachments, users, projects, versions, boards, sprints, filters, dashboards, and properties. However, delete operations are largely missing for issues, comments, worklogs, links, attachments, and boards/sprints/filters/dashboards, leaving notable lifecycle gaps.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.
      141 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with JIRA through MCP, providing 35 tools for issues, comments, transitions, projects, boards, sprints, epics, links, worklogs, versions, attachments, users, and fields.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Jira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.
      MIT