"How to manage Jira tickets effectively" matching MCP servers:

Enables semantic search and analysis of customer support tickets. Provides tools to search tickets, analyze the dataset, and retrieve individual tickets using natural language.

A read-only MCP server exposing TOTVS support tickets (Portal do Cliente) as tools for LLMs in Claude Code, Claude Desktop, and Cursor.

Enables support engineers to investigate a ticket by cross-referencing simulated Zendesk, Datadog, Snowflake, and AWS data, returning a possible root cause, ranked hypotheses with evidence, and recommended checks.

Enables asking questions in plain English about 61,765 customer-support tickets, returning exact answers computed via SQL queries over DuckDB.

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

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

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

A Model Context Protocol server that connects your AI IDE to Jira. Query your tickets, active sprint, and issue details directly from GitHub Copilot, Cursor, Claude Desktop, or any MCP-compatible client.

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 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.

Enables agents to convert Markdown into WhatsApp-compatible formatting, including styled text, lists, and tables that fit a phone's monospace width.

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.

AI-powered MCP server for file renaming, organization, and PDF splitting using natural language prompts and content analysis.

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.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

MCP server that connects to Jira Data Center, enabling issue search, retrieval, creation, comments, workflow transitions, project listing, arbitrary JQL, and turning meeting notes into structured Jira stories, tasks, and bugs.

Enables searching and retrieving documentation from crawled documentation sites as an MCP server, allowing coding agents to query real docs instead of relying on training data.