Jira MCP Server

Most planning and project tracking work still happens through a UI a human drives. Jira MCP server moves it into the conversation instead. An MCP server compatible with Jira V2 and V3 api and custom fields.

The short version

Enhanced Model Context Protocol server for interacting with Jira directly from Claude.

• Full Jira API Integration — Comprehensive access to Jira functionality
• Enhanced Formatting — Improved Markdown to Atlassian Document Format (ADF) conversion with support for code blocks and inline formatting
• Input Validation — Robust schema validation using Zod
• Improved Error Handling — Detailed error messages and graceful error recovery
• Custom Field Support — Easy configuration for working with custom Jira fields
• Status Transitions — Advanced workflow management

The tools it exposes

The server publishes 1 tool. What each one is for:

• Contributing — Contributions are welcome! Please feel free to submit a Pull Request

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

Configuration is passed through the environment: JIRA_HOST, JIRA_EMAIL, JIRA_API_TOKEN, JIRA_API_VERSION, JIRA_CUSTOM_FIELDS, LOG_LEVEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18 or higher - Jira Cloud or Server instance - Jira API token (for Cloud) or username/password (for Server) - Claude Desktop or other MCP-compatible AI assistant

How it compares

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Jira's toolset — Contributing — is a fair guide to whether it matches your workflow. It is maintained by fkesheh; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Jira's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.