Skip to main content
Glama

jiri-mcp — Jira MCP Server

An MCP (Model Context Protocol) server that connects AI agents to Jira Cloud, enabling natural language issue management.

Features

Tool

Description

search_issues

Search issues with JQL

get_issue

Get full issue details

create_issue

Create new issues

update_issue

Update issue fields

add_comment

Add comments

list_transitions

List available status transitions

transition_issue

Change issue status

assign_issue

Assign/unassign issues

list_projects

List accessible projects

search_users

Search users by name/email

Related MCP server: Jira Extended MCP Server

Setup

1. Install dependencies

npm install

2. Configure environment

Copy the example env file and fill in your credentials:

cp .env.example .env

You'll need:

  • JIRA_HOST — Your Jira Cloud URL (e.g., https://yourcompany.atlassian.net)

  • JIRA_EMAIL — Your Atlassian account email

  • JIRA_API_TOKEN — API token from Atlassian API Tokens

3. Build

npm run build

Usage

With Antigravity

Copy mcp_config.json to your Antigravity config directory and update the environment variables:

# Global config (all projects)
cp mcp_config.json ~/.gemini/config/mcp_config.json

# Or project-specific
cp mcp_config.json .agents/mcp_config.json

Edit the copied file to add your real credentials:

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["/absolute/path/to/jiri-mcp/dist/index.js"],
      "env": {
        "JIRA_HOST": "https://yourcompany.atlassian.net",
        "JIRA_EMAIL": "you@example.com",
        "JIRA_API_TOKEN": "your-api-token"
      }
    }
  }
}

Development mode

npm run dev

Production

npm run build
npm start

Example prompts

Once connected, you can ask your AI agent things like:

  • "Search for open bugs in project MYAPP"

  • "What's the status of MYAPP-123?"

  • "Create a task in MYAPP: Fix login timeout with priority High"

  • "Move MYAPP-456 to In Progress"

  • "Add a comment to MYAPP-789: Deployed fix to staging"

  • "Who's assigned to MYAPP-321?"

License

MIT

Available Tools

10 tools
add_commentB

Add a comment to a Jira issue.

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

assign_issueA

Assign a Jira issue to a user by their account ID. Use search_users to find a user's account ID. Pass an empty accountId to unassign.

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

create_issueA

Create a new Jira issue. Requires project key, summary, and issue type. Optionally set description, assignee, labels, and priority.

Inputs: summary (required), projectKey (required), labels, priority, +3 more.

get_issueA

Get full details of a single Jira issue by its key (e.g., PROJ-123). Returns summary, status, description, comments, and metadata.

Inputs: issueKey (required).

list_projectsA

List all Jira projects accessible to the authenticated user.

Inputs: no named parameters.

list_transitionsA

List available status transitions for a Jira issue. Use this to discover valid transition IDs before calling transition_issue.

Inputs: issueKey (required).

search_issuesA

Search Jira issues using JQL (Jira Query Language). Returns a summary table of matching issues. Example JQL: 'project = PROJ AND status = "In Progress" ORDER BY updated DESC'

Inputs: jql (required), maxResults.

search_usersA

Search for Jira users by name or email. Returns account IDs which can be used for assignment.

Inputs: query (required).

transition_issueA

Transition a Jira issue to a new status. Use list_transitions first to get valid transition IDs.

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

update_issueA

Update fields on an existing Jira issue. Only the provided fields will be changed; others remain untouched.

Inputs: issueKey (required), labels, summary, priority, +2 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a clearly distinct Jira operation: creation, retrieval, updating, searching, commenting, transitions, assignment, projects, and user lookup. The closely related list_transitions and transition_issue are deliberately separated into discovery and execution steps.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern, such as create_issue, list_projects, and search_users. The naming style is uniform and predictable across the entire set.

    Tool Count5/5

    Ten tools is well-scoped for a Jira MCP server, covering core issue management without unnecessary bloat. Every tool serves a useful, non-redundant purpose in the workflow.

    Completeness4/5

    The tool surface covers the core Jira lifecycle: create, read, update, search, comment, transition, assign, plus project and user lookup. Minor gaps remain, such as issue deletion or attachment handling, but they are not essential for typical agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers