"An official MCP server for Jira" matching MCP servers:

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables creating Jira issues and listing issue types for a Jira Cloud project using Basic Auth credentials.

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

Enables an AI agent to manage Jira Stories in a self-hosted Jira instance via the Jira REST API v2, including CRUD operations, workflow transitions, and burndown data retrieval.

MCP server for Jira Cloud that lets AI agents search, read, and write Jira issues using your own Atlassian account and API token, with write operations gated behind explicit opt-in.

An MCP server for interacting with Atlassian Jira, enabling issue management, attachments, and other operations via natural language.

An MCP server that provides tools to interact with JIRA for sprint management, issue tracking, and attachment handling.

An MCP server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It enables users to perform CRUD operations on issues, search with JQL, manage comments, and list projects through the Jira REST API.

A TypeScript-based server that enables Cursor editor to interact with Jira tickets for viewing, creating, commenting on, and updating tickets directly from the editor.

Provides capabilities for searching Jira issues using JQL and retrieving detailed issue information.

MCP server for fetching Jira issue data via the Jira API.

An MCP server for integrating with Jira Server instances, enabling natural language interactions to create, update, search, and manage issues and comments.

Jira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.

MCP server for Jira Cloud — gives AI agents full context and control over Jira issues, projects, sprints, and workflows.

Enables AI agents and users to verify claims about Jira issues and issue counts against live Jira, retrieve verifiable facts for drafting updates, and re-check previously posted claims. It provides read-only tools and an issue panel so status updates can be evidence-based and mismatches corrected before or after posting.

An MCP server for Jira that enables comprehensive issue management, sprint operations, comments, attachments, and batch processing with localization and flexible date support.

Enables Jira integration for comprehensive issue management, board operations, time tracking, and project management through natural language.

A simple MCP server that provides access to Jira issues from Cursor AI, allowing users to reference and query Jira tickets directly in the chat panel.

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.

A plugin-oriented Jira capability kernel for AI models, providing 24+ tools for Jira operations including issue search, comments, transitions, and project analysis via a dispatcher and HTTP service.

Exposes JIRA sprint data as MCP tools and prompts, with mock data and a pluggable client for real JIRA integration.

Pay-per-call USDC payment proxy for AI agents. Issue scoped Pay Tokens with hard spending caps and auto-journal every charge to freee / Money Forward / QuickBooks.

Enables Codex to consult Claude Code for a second opinion through a local stdio MCP server, exposing the ask_claude tool for text-only reviews and recommendations using existing Claude Code authentication. Codex can request findings and tradeoff analysis without allowing Claude to edit files or run commands.

Real human judgment as agent tools -- an AI agent can ask a question and get back a structured, schema-validated JSON answer from a real quality-scored human. 16 response types (yes/no, ratings, rankings, A/B tests, sentiment, image/video/audio review, voice/video/photo capture). Fully programmatic signup with a $5 free trial credit, no card required.

Industry 4.0 / IIoT AI agents for manufacturing: explain OEE losses per shift, triage machine alarms, find downtime root causes, prepare predictive-maintenance jobs and write shift reports from Unified Namespace (UNS), MQTT or historian data. Plus an industrial AI-readiness diagnostic and a vendor-neutral digital-transformation advisor. Works in Claude Code, Codex and any MCP client.

Free Industry 4.0 / IIoT tools, no API key or account: lint MQTT Sparkplug B topics, check a Unified Namespace (UNS) for naming and hierarchy problems, and run an industrial AI-readiness diagnostic for manufacturing digital transformation and smart-factory projects. Works in Claude Code, Codex and any MCP client.

Enables logging time entries to Jira Cloud issues, including adding worklogs, listing existing entries, and verifying credentials.

Enables coding agents to read Jira Cloud issues, search via JQL, and retrieve comments, attachments, and change history through a lightweight, context-efficient MCP toolset.

Integrates Google's Gemini AI models into Claude Code and other MCP clients to provide second opinions, code comparisons, and token counting. It supports streaming responses and multi-turn conversations directly within your existing AI development workflow.

Provides read-only access to Jira, enabling users to retrieve issue details, comment threads, linked-issue context, epic children, and JQL search results as compact Markdown.