mcp-jira

MCP server from 1broseidon/mcp-jira-server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio 1broseidon-mcp-jira-server node /path/to/jira-server/build/index.js \
  --env JIRA_EMAIL="your-email@example.com" \
  --env JIRA_DOMAIN="your-domain" \
  --env JIRA_API_TOKEN="your-api-token"

How to use

This MCP server provides a Jira integration for AI assistants, exposing a set of tools to manage Jira issues directly from the Model Context Protocol. You can create issues (Task, Epic, Subtask), list issues with optional status filtering, update issue fields, retrieve detailed issue information, delete issues, and add comments to existing issues. Each tool expects a working_dir that contains your Jira configuration (e.g., .jira-config.json) and relies on your Jira credentials provided via environment variables. Use the tools to perform common Jira workflows from natural language prompts or automated agents.

To use the tools, configure your environment with your Jira credentials (email, API token, and domain) and point the tool at your Jira project(s) via the .jira-config.json file. For example, create or update issues with create_issue by providing summary, description, and type; fetch status or details with get_issue or list_issues; modify fields with update_issue; add context with add_comment; and maintain project scope with the projectKey settings in .jira-config.json.

How to install

Prerequisites:

Node.js installed on your system
Access to a Jira account with API token

Installation via Smithery (recommended):

Install the Jira Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install jira-server --client claude

Manual installation:

Install dependencies:

npm install

Build the server:

npm run build

Ensure your Jira configuration file (.jira-config.json) is present in your working directory and that environment variables for Jira are set as described in the mcp_config.

Configure MCP server in your environment as shown in the Configuration section of the README to wire the server into your Claude setup.

Additional notes

Tips and notes:

Ensure .jira-config.json exists in the working directory and lists the Jira project keys you intend to manage.
Set JIRA_EMAIL, JIRA_API_TOKEN, and JIRA_DOMAIN in the MCP environment to authenticate with Jira.
If you change project keys, update the .jira-config.json accordingly.
The server supports status filtering for list_issues; use standard Jira statuses like "To Do", "In Progress", and "Done".
For best results, enable auto-rebuild/watch mode during development with npm run watch.
Check error handling covers invalid project keys, missing configuration, invalid issue types, authentication errors, and invalid status transitions.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.