Skip to main content
Glama

Jira MCP Server

MCP (Model Context Protocol) server for Jira Cloud API integration. Create issues and list issue types using Basic Auth (email + API token).

Features

  • jira_create_issue – Create a new Jira issue with project, summary, and issue type

  • jira_list_issue_types – List available issue types for a project

Related MCP server: mcp-jira

Prerequisites

Setup

  1. Clone and install

    cd jira_mcp
    npm install
  2. Configure environment

    Copy .env.example to .env and fill in your values:

    cp .env.example .env
    JIRA_BASE_URL=https://your-domain.atlassian.net
    JIRA_EMAIL=user@example.com
    JIRA_API_TOKEN=your_api_token_here
  3. Build

    npm run build

Usage

Run the server

npm start

Or with env vars inline:

JIRA_BASE_URL=https://your-domain.atlassian.net JIRA_EMAIL=you@example.com JIRA_API_TOKEN=xxx npm start

The server runs via stdio and is intended to be used as a subprocess by MCP clients (e.g. Cursor, Claude Desktop).

Cursor configuration

Add to your Cursor MCP config (e.g. ~/.cursor/mcp.json):

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["/path/to/jira_mcp/dist/index.js"],
      "env": {
        "JIRA_BASE_URL": "https://your-domain.atlassian.net",
        "JIRA_EMAIL": "your-email@example.com",
        "JIRA_API_TOKEN": "your-api-token"
      }
    }
  }
}

Tools

jira_list_issue_types

List issue types (Bug, Task, Story, etc.) for a project.

Parameter

Type

Required

Description

project_key

string

Yes

Jira project key (e.g. PROJ)

response_format

string

No

markdown (default) or json

jira_create_issue

Create a new Jira issue.

Parameter

Type

Required

Description

project_key

string

Yes

Jira project key

summary

string

Yes

Issue title

issue_type

string

Yes

Issue type name (e.g. Bug, Task) or ID

description

string

No

Issue description

response_format

string

No

markdown (default) or json

Testing Without Cursor

The best way to test the MCP server interactively is with MCP Inspector, a web UI for exercising tools, resources, and prompts.

  1. Build the project (if not already done):

    npm run build
  2. Run MCP Inspector with your server. With a .env file in the project root, the server loads it automatically:

    npm run inspector

    Or run directly (env from .env is loaded by the server):

    npx @modelcontextprotocol/inspector node dist/index.js

    To pass env vars explicitly instead:

    npx @modelcontextprotocol/inspector \
      -e JIRA_BASE_URL=https://your-domain.atlassian.net \
      -e JIRA_EMAIL=you@example.com \
      -e JIRA_API_TOKEN=your-token \
      node dist/index.js
  3. Open the Inspector in your browser (typically http://localhost:6274).

  4. Test tools – Use the Tools tab to call jira_list_issue_types and jira_create_issue with sample inputs.

The Inspector runs your server as a subprocess and connects via stdio, so it behaves like a real MCP client.

Development

# Run with auto-reload
npm run dev

# Run all tests (unit + integration)
npm test

# Run tests with coverage
npm run test:coverage

# Run integration tests only (spawns MCP server + mock Jira)
npm run test:integration

# Lint code
npm run lint
npm run lint:fix

# Format code
npm run format
npm run format:check

Pre-commit hooks (Husky)

On each git commit, Husky runs lint and Prettier on staged files. If there are errors, the commit is blocked with a message:

❌ Commit blocked: Fix the lint or Prettier errors above.
   Tips: npm run lint:fix  |  npm run format

To bypass (use sparingly): git commit --no-verify or HUSKY=0 git commit

CI

GitHub Actions runs on pull requests to main/master with separate stages on Node.js 24.x:

  • Unit Tests – npm run test:unit (90% coverage enforced)

  • Integration Tests – npm run test:integration (MCP server + mock Jira)

  • Lint & Format – ESLint and Prettier checks

  • Security Audit – npm audit (fails on moderate+ vulnerabilities)

  • CodeQL – Static security analysis (JavaScript/TypeScript)

  • Dependency Review – Checks for vulnerable deps in PRs

Dependabot is configured for weekly dependency updates (.github/dependabot.yml).

To block merges until PRs pass, enable branch protection in GitHub: Settings → Branches → Add rule → Require status checks to pass before merging.

API Reference

License

MIT

Available Tools

2 tools
jira_create_issueCreate Jira IssueA

Create a new Jira issue in a project.

Creates an issue with the given project, summary, and issue type. Use jira_list_issue_types to discover valid issue types for a project.

Args:

  • project_key (string): Jira project key (e.g. PROJ)

  • summary (string): Issue title (required)

  • issue_type (string): Issue type name (e.g. Bug, Task) or numeric ID

  • description (string, optional): Issue description

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON: { "key": string, "id": string, "self": string } For Markdown: Summary with issue key and link

Examples:

  • Create a bug: project_key="PROJ", summary="Login fails", issue_type="Bug"

  • Create a task: project_key="DEMO", summary="Review docs", issue_type="Task"

Error Handling:

  • 401: Check JIRA_EMAIL and JIRA_API_TOKEN

  • 403: No create permission in project

  • 404: Project or issue type not found

  • 422: Validation error (e.g. missing required fields)

Inputs: summary (required), issue_type (required), project_key (required), description, +1 more.

jira_list_issue_typesList Jira Issue TypesA
Read-onlyIdempotent

List issue types available for a Jira project.

Use this tool to discover which issue types (e.g. Bug, Task, Story) can be used when creating issues in a project. Returns id, name, and description for each type.

Args:

  • project_key (string): Jira project key (e.g. PROJ, DEMO)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON: { "issue_types": [{ "id": string, "name": string, "description": string }] } For Markdown: Formatted list of issue types

Examples:

  • "What issue types can I create in project PROJ?" -> project_key="PROJ"

  • Use before jira_create_issue to get valid issue_type values

Error Handling:

  • 401: Check JIRA_EMAIL and JIRA_API_TOKEN

  • 403: Insufficient permissions for the project

  • 404: Project not found

Inputs: project_key (required), response_format.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are completely distinct: one lists issue types for discovery, the other creates an issue. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow the same 'jira_verb_noun' pattern (jira_list_issue_types, jira_create_issue), making the naming predictable and consistent.

    Tool Count3/5

    With exactly 2 tools, the server sits in the 'borderline thin' range. While the scope is clear, a Jira server typically needs more tools to be useful.

    Completeness2/5

    The tools cover only creation and issue-type lookup. Missing get, update, delete, search, and project listing means agents cannot verify or manage issues, leaving significant workflow gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Jira issues, projects, and comments via API Key. Supports operations like creating, updating, searching, transitioning issues, and managing projects.
      708 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.
      9
      31 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables creating, fetching, and updating Jira issues via the REST API with support for ADF descriptions and common fields like priority, labels, and issue types.
      1,667 npm
      2
      Apache 2.0