"Information about Jira Integration" 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.

Exposes enterprise tools to third-party AI agents through a single guard that authorizes each call against default-deny, purpose-scoped entitlements, executes it, and writes a hash-chained, tamper-evident decision trace the firm owns. It also verifies signed vendor webhooks and enforces a strict versioned contract, so agent activity stays scoped, auditable, and portable across vendors.

Enables natural language control of quantum photonics experiments through the qudi framework. Supports safe instrument control, measurement execution, and safety system management with built-in runlevel protection and parameter validation.

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.

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.

Enables voice-controlled Instagram account management from the Mac notch, including reading insights, comments, DMs, and publishing photos or carousels via natural language, with scheduled publishing and secure photo handling.

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

Lets AI agents work with self-hosted Jira Server/Data Center 7-10 using a plain username + password, no API tokens. 42 tools for issues, JQL search, transitions, comments, worklogs and sprints.

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.

MCP server for IG's REST Trading API and Lightstreamer streaming API. Provides tools for accounts, markets, positions, orders, watchlists, sentiment, OTC trades, and streaming price/account/trade/chart data.

Enables AI agents to interact with Jira and GitHub through MCP tools, including searching, creating, commenting on, and transitioning Jira issues and listing pull requests, summarizing diffs, creating issues, and commenting on GitHub.

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 Model Context Protocol server that enables integration with JIRA, allowing users to interact with JIRA tasks and issues through Claude AI assistant.

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.

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.

Provides read and write access to Atlassian Jira Assets (formerly Insight) via MCP, enabling AI clients to fetch objects, discover schemas, update fields, and apply bulk changes. Includes a review dashboard for bulk editing.

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.

Connects to Jira with Xray Test Management to extract test cases related to tickets and list test executions.

Fetches Jira attachments and returns them inline (for small images) or as local paths for larger files and other types, enabling AI models to access Jira attachments directly.

Local MCP server for Jira Server/Data Center providing read-only tools and queued write operations that require manual approval via a local web UI.

MCP Server to log time and view Jira statistics directly from Cursor IDE.

An MCP server for end-to-end Jira and GitHub integration, enabling AI agents in the IDE to automate workflows from issue tracking to pull request management.

Enables interaction with self-hosted Jira instances via Personal Access Token, supporting issue management and project operations through natural language.

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.

A Python-based server allowing seamless integration with JIRA for managing and interacting with projects through custom APIs.

Custom MCP server for interacting with Jira, supporting issue management, search, and project operations.

Enables MCP clients to query and modify Jira Server/Data Center and Confluence through a local Chrome login session cookie instead of a token. It includes upstream Jira and Confluence tools, with optional read-only mode to disable writes.

A local-only MCP server providing safe, typed Jira tools for AI agents via Atlassian ACLI, enabling search, get issue, add comment, and transition issues with policy guardrails.