"Accessing Jira Tickets and Updating Their State" 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.

A stateless MCP server for AI film and video production that tracks project state, shot status, and updates, enabling consistent characters and continuity across generative video tools.

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.

Graph-native bounded working memory for coding agents with typed memories, causal retrieval, current-vs-stale state queries, and compact small-model briefs.

Enables validating, simulating, and analyzing finite state machines via MCP tools for step execution, path finding, and schema inspection.

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

Enables AI agents to call 33 pay-per-call tools for onchain data, ECB exchange rates, text utilities, and more, using USDC on Base over x402 with optional prepaid credit or wallet-based payments.

Provides state and log management tools designed for long-lived AI agents that may be interrupted and resumed. It enables tracking agent progress and maintaining an append-only event history to ensure continuity across multiple sessions.

Persistent, branch-aware workflow state memory MCP server for AI coding assistants. Tracks tasks, accepted decisions, and active blockers to prevent session context bloat and speed up development.

A small MCP server that stores and retrieves compact decision-relevant state (goals, constraints, facts, decisions) outside the chat context, enabling easy retrieval for Claude Code or Codex.

Enables agents to access local physiological context—Libre glucose, heart-rate, and watch history—with provenance and freshness metadata, so they can recognize when a user seems unusually off.

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

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.

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.

MCP server that scans multi-language codebases to detect stubs, missing imports, and structural incompleteness, assigning drift scores to quantify LLM context erosion.

Enables Claude to read Jira CSV/JSON backlog exports, audit tickets for test readiness, and generate validated Gherkin acceptance scenarios tied to ticket criteria. It also tracks acceptance-criteria coverage and flags ambiguities or missing information for Product Owner follow-up.

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.

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.

SQLite-backed MCP server for Claude Code session persistence and multi-agent coordination. Provides tools for session management, event logging, decision tracking, file locking, agent registry, and plan tracking.

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.

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