"Managing and Processing Jira Tickets" 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.

An MCP server that enables AI assistants to create and run Processing sketches directly through natural language commands.

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

Enables image processing tasks such as resizing, compressing, converting formats, cropping, and extracting metadata directly within IDEs like Cursor via the Model Context Protocol.

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.

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

Relays a result screenshot to Slack so you can review a coding agent's output without opening the app.

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.

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.

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.

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.

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.

A Scrum-aware MCP server that provides semantic analysis of Jira issues, sprint health, and Agile workflow intelligence, returning structured summaries and recommendations instead of raw Jira payloads.

Enables read-only Jira Data Center insights by default, with opt-in audited write tools, sprint and release health summaries, and structured issue search via MCP.