Skip to main content
Glama
Sign In
deenesjakoruzh
Jira MCP Server

Jira MCP Server

by ashu-arora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Jira MCP Server

An MCP (Model Context Protocol) server that connects VS Code Copilot to your Jira instance – Cloud, Server, or Data Center.

Quick Setup

1. Install & build

cd jira-mcp-server
npm install
npm run build

2. Configure credentials

Copy the example and fill in your values:

cp .env.example .env

Edit .env:

# Your Jira site URL
JIRA_BASE_URL=https://yourcompany.atlassian.net

# Your email (Cloud) or username (Server)
JIRA_EMAIL=you@yourcompany.com

# API token (Cloud) or Personal Access Token (Server)
JIRA_API_TOKEN=your-token-here

# "cloud" or "server"
JIRA_AUTH_TYPE=cloud

Where to get your token

Platform

How

Atlassian Cloud

Go to API Tokens → Create API token

Jira Server/DC

Go to your Jira profile → Personal Access Tokens → Create token

3. Connect to VS Code

Add this to your VS Code settings.json (or workspace .vscode/settings.json):

{
  "mcp": {
    "servers": {
      "jira": {
        "command": "node",
        "args": ["/absolute/path/to/jira-mcp-server/dist/index.js"],
        "env": {
          "JIRA_BASE_URL": "https://yourcompany.atlassian.net",
          "JIRA_EMAIL": "you@yourcompany.com",
          "JIRA_API_TOKEN": "your-token-here",
          "JIRA_AUTH_TYPE": "cloud"
        }
      }
    }
  }
}

Tip: Replace /absolute/path/to/jira-mcp-server with the actual path on your machine.

Related MCP server: Jira Stories MCP Server

Available Tools

Tool

Description

search_issues

Search issues with JQL

get_issue

Get full details of an issue by key

create_issue

Create a new issue

update_issue

Update fields on an existing issue

add_comment

Add a comment to an issue

get_transitions

List available status transitions

transition_issue

Move an issue to a new status

assign_issue

Assign an issue to a user

list_projects

List all accessible projects

get_myself

Get the authenticated user's profile

Example Prompts (in Copilot Chat)

  • "Show me Jira issues assigned to me"

  • "Get details of PROJ-123"

  • "Create a bug in project PROJ: Login page crashes on Safari"

  • "Move PROJ-456 to In Progress"

  • "Add a comment to PROJ-789: Fixed in commit abc123"

Available Tools

10 tools
add_commentC

Add a comment to a Jira issue.

Inputs: body (required), issueKey (required).

assign_issueA

Assign a Jira issue to a user. For Cloud use accountId, for Server use username.

Inputs: assignee (required), issueKey (required).

create_issueB

Create a new Jira issue in a project.

Inputs: summary (required), projectKey (required), issueType, description.

get_issueA

Get full details of a single Jira issue by its key (e.g. PROJ-123).

Inputs: issueKey (required).

get_myselfA

Get the profile of the currently authenticated Jira user.

Inputs: no named parameters.

get_transitionsA

Get available status transitions for an issue (useful before transitioning).

Inputs: issueKey (required).

list_projectsA

List all Jira projects accessible to the authenticated user.

Inputs: no named parameters.

search_issuesA

Search Jira issues using JQL. Returns key, summary, status, assignee, priority, and type.

Inputs: jql (required), maxResults.

transition_issueA

Transition a Jira issue to a new status. Use get_transitions first to find the right transition ID.

Inputs: issueKey (required), transitionId (required), comment.

update_issueB

Update fields on an existing Jira issue.

Inputs: fields (required), issueKey (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: search vs. get, create vs. update, comment, transitions, assignment, project listing, and user profile. There is no ambiguity between tools; an agent can reliably select the correct one based on the action needed.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., search_issues, get_issue, create_issue, add_comment). Even the 'get_*' tools differ by object (issue, transitions, myself), maintaining predictability. No mixed conventions or vague verbs.

    Tool Count5/5

    With 10 tools, the server is well-scoped for Jira's core functionality. Each tool serves a necessary purpose, covering create, read, update, search, comments, transitions, assignment, and user/project context. No redundancy or bloat.

    Completeness4/5

    The set covers the primary Jira workflows: issue lifecycle (create, get, update, transition, assign), search, comments, and context (projects, user). Minor gaps exist (e.g., no delete_issue, no link_issue), but these are not critical for most automation tasks and can be worked around.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers