Jira

You run a Jira MCP Server that connects your Jira workflows to an AI assistant, enabling practical automation like retrieving issue details, managing sprints, linking work across development tools, and capturing development information in one place. This server is built around real-world Jira usage patterns, giving you actionable tools to streamline development, sprint planning, and release visibility.

How to use

You interact with Jira MCP through an MCP client or Cursor-like interface. Use commands and prompts that reflect common Jira workflows, such as asking for an issue’s status, listing active or future sprints, creating and updating issues, adding comments or worklogs, and retrieving development information linked to an issue. The server exposes a focused set of tools designed to help you manage issues, sprints, transitions, comments, worklogs, history, relationships, versions, and development data from connected repositories.

How to install

Prerequisites: you need either Docker or a local binary to run the Jira MCP server. You also need a Jira API token for authentication.

Step 1. Get an API token. Create one at the Atlassian API token page.

Step 2. Choose a.run method and prepare your MCP configuration.

Step 3. Start the Jira MCP server using one of the provided configurations.

Configuration and start options

You configure the server by providing environment variables and runtime commands. The examples below show two explicit ways to run the Jira MCP server: via Docker or as a local binary. In both cases you supply your Jira host, account email, and API token.

{
  "mcpServers": {
    "jira": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "ATLASSIAN_HOST=https://your-company.atlassian.net",
        "-e", "ATLASSIAN_EMAIL=your-email@company.com",
        "-e", "ATLASSIAN_TOKEN=your-api-token",
        "ghcr.io/nguyenvanduocit/jira-mcp:latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "jira": {
      "command": "/usr/local/bin/jira-mcp",
      "env": {
        "ATLASSIAN_HOST": "https://your-company.atlassian.net",
        "ATLASSIAN_EMAIL": "your-email@company.com",
        "ATLASSIAN_TOKEN": "your-api-token"
      }
    }
  }
}

Available tools

jira_get_issue

Retrieve detailed information about a specific issue including status, assignee, description, subtasks, and available transitions

jira_create_issue

Create a new issue with specified details (returns key, ID, and URL)

jira_create_child_issue

Create a child issue (sub-task) linked to a parent issue

jira_update_issue

Modify an existing issue's details (supports partial updates)

jira_list_issue_types

List all available issue types in a project with their IDs, names, and descriptions

jira_search_issue

Search for issues using JQL with customizable fields and expand options

jira_list_sprints

List all active and future sprints for a specific board or project

jira_get_sprint

Retrieve detailed information about a specific sprint by its ID

jira_get_active_sprint

Get the currently active sprint for a given board or project

jira_search_sprint_by_name

Search for sprints by name with exact or partial matching

jira_list_statuses

Retrieve all available issue status IDs and their names for a project

jira_transition_issue

Transition an issue through its workflow using a valid transition ID

jira_add_comment

Add a comment to an issue (uses Atlassian Document Format)

jira_get_comments

Retrieve all comments from an issue

jira_add_worklog

Add a worklog entry to track time spent on an issue

jira_get_issue_history

Retrieve the complete change history of an issue

jira_get_related_issues

Retrieve issues that have a relationship (blocks, is blocked by, relates to, etc.)

jira_link_issues

Create a link between two issues, defining their relationship

jira_get_version

Retrieve detailed information about a specific project version

jira_list_project_versions

List all versions in a project with their details

jira_get_development_information

Retrieve branches, pull requests, and commits linked to an issue via development tool integrations