@dario-motta/jira-mcp-server

Jira MCP server for safe Jira reads and writes from compatible AI clients.

Install

Requirements: Node.js 22+, npm, a Jira REST v2 base URL, and a Jira token with the required project permissions.

npx @dario-motta/jira-mcp-server setup

The guided setup registers the published package through npx -y, stores only the required Jira variables in the selected host configuration, and verifies the Jira connection. It creates neither a project dependency nor a .env file. Restart the MCP host when it completes.

Supported targets are Claude Code and Codex through their native registration commands, plus Copilot, Claude Desktop, Cursor, and Windsurf through their MCP configuration files. Non-interactive setup must specify --install-mode native|file.

npx @dario-motta/jira-mcp-server doctor

For a standalone check, export the Jira variables first (or keep a legacy .env file in the selected project). Guided setup already performs this verification with the supplied credentials.

For step-by-step installation, certificates, and configuration regeneration, see docs/INSTALL.md.

What it does

• Reads issues, comments, transitions, projects, boards, sprints, and releases.
• Creates issues, assigns users, and manages comments and transitions.
• Protects write operations with audit entries, mandatory bulk preview/confirmation, and explicit issue-bound confirmation for permanent deletion.
• Supports Jira Cloud and falls back to Jira Server REST v2 where the corresponding Cloud endpoint is unavailable.

Documentation

• Installation
• Tool usage and safe workflows
• Release runbook
• Changelog

Security

• Never commit host configuration files containing Jira tokens.
• Use least-privilege tokens and rotate them regularly.
• Avoid passing --token in shared terminals because shell history can retain it.
• Use delete_issue only for test or explicitly approved issues: deletion is permanent.