"Jira" matching MCP servers:

An async MCP server for JIRA integration, enabling AI assistants to search, create, and manage JIRA issues via JQL and other operations.

Exposes Jira task management (list, create with two-step confirmation, start) to AI agents while keeping credentials hidden, and deliberately does not handle git operations.

MCP server for Jira Cloud enabling issue tracking, comments, transitions, and attachments management through natural language.

Enables AI clients to search, read, create, and update Jira Server/Data Center issues, comments, and attachments, and to move issues through workflow transitions using Personal Access Token authentication. It also supports file uploads and downloads from allowlisted local paths, plus paginated search and issue-detail retrieval including links and attachment metadata.

Connects MCP clients to Jira Server / Data Center through REST API v2, letting users search, create, update, comment on, transition, link, and log work on issues in natural language. Read-only tools are enabled by default, while write and delete capabilities require explicit CLI flags.

A local MCP server for safely managing personal Jira Cloud issues through ACLI, reusing an existing OAuth session without storing credentials. It enables listing, searching, and reading assigned issues, ranking potential duplicates, and making confirmed updates like comments, transitions, and field changes.

Enables MCP-compatible editors to connect to Jira Cloud with a user-supplied API token, verify the connection, and fetch issue details through natural-language requests.

Jira Pilot is an MCP server that provides 14 tools for AI assistants to manage Jira issues, sprints, boards, and more. It enables natural language interaction with Jira through the Model Context Protocol.

Enables local MCP-based interaction with Jira Cloud, offering tools for issues, comments, transitions, worklogs, attachments, and user lookups while addressing gaps like attachment downloads, mention notifications, and multi-step status transitions.

A lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.

Enables read-only retrieval of Jira Cloud issues, JQL search, and project issue listing through MCP tools.

Enables AI clients to interact with a mock JIRA-shaped issue tracker through MCP tools for managing projects, issues, and users.

A one-click Jira integration for AI coding tools like Claude Desktop, Cursor, and VS Code, enabling create, read, update, move, comment, and search operations on Jira tickets directly from the assistant.

MCP server that connects opencode with Jira Cloud, exposing issue tracking, project management, and agile features as structured tools for AI agents.

MCP server for logging and checking Jira Cloud worklogs from AI agents such as Claude Code, Claude Desktop, Cursor, or any MCP client that supports stdio.

Enables coding agents to turn Jira Cloud tickets into ready-to-build briefs, verify local branches against acceptance criteria, and prepare QA handoffs, with optional previewed and audited write-back.

Enables AI assistants to manage Jira issues with full CRUD, transitions, linking, commenting, and file attachments via the Jira REST API v3.

Gives local coding agents safe, read-only access to an existing Jira instance through MCP over stdio, keeping Jira credentials out of the LLM. It exposes tools for reading issues, comments, linked items, JQL search results, assigned open issues, and project metadata.

Stdio-based MCP server exposing Jira tools for searching, creating, getting, commenting on, assigning, and transitioning issues, as well as listing projects, with authentication via token or basic auth.

Enables an AI coding agent to scan a day's git commits across work repositories and group them into Jira tickets, creating or updating them with estimates and logged time. It also surfaces actionable, categorized errors so an agent knows what failed and whether to retry.