"Jira" matching MCP servers:

Provides AI assistants with tools to query, filter, and analyze JIRA issues stored in Snowflake, enabling natural language interaction with issue data.

A Model Context Protocol server that provides access to JIRA issue data stored in CSV files, enabling AI assistants to query, filter, and analyze JIRA issues through standardized tools.

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 intelligent analysis of regression test failures and automatic discovery of solutions in JIRA. Analyzes test logs using AI-driven algorithms and matches errors with relevant JIRA issues through natural language interactions.

This read-only MCP Server allows you to connect to Jira data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).

Integrates Jira with Cursor IDE for AI-powered issue management, sprint tracking, library vulnerability analysis, and MySQL database queries through natural language.

This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Jira Assets (beta): https://www.cdata.com/download/download.aspx?sku=KNZK-V&type=beta

This project builds a read-only MCP server. For full read, write, update, delete, and action capabilities and a simplified setup, check out our free CData MCP Server for Jira Service Management (beta): https://www.cdata.com/download/download.aspx?sku=GKZK-V&type=beta

An MCP server for managing agent memory using provenance tracking, decay-weighted retrieval, and feedback loops to optimize information recall. It allows agents to store insights in a local SQLite database and rank them based on confidence, age, and usefulness.

Enables AI assistants to search and browse Jira Service Management Assets data using AQL queries, schema exploration, and hierarchical object searches. It features robust automatic pagination to ensure reliable retrieval of complete asset datasets.

Enables AI agents and IDE copilots to reach Jira, Neo4j, Teradata, and a business rule engine through one governed, multi-tenant endpoint that applies authentication, role-based tool authorization, guardrail checks, layered rate limiting, audit logging, and envelope encryption. It also exposes a live Neo4j graph schema resource and a Cypher-composition guidance prompt so clients can discover and query connected data safely.

Connects Claude Desktop to self-hosted enterprise tools such as Confluence, Jira, Bitbucket, Airtable, and databases (MySQL, MariaDB, ClickHouse, Oracle) via MCP.

Keeps Jira Cloud, Jira Server, Linear or its own built-in tracker (plus Confluence pages) in one local SQLite file. Its MCP tools answer from that file: read-only SQL, full-text search across issues, comments and wiki pages, issue detail, sprint and retro reads.

Enables an event-driven operations agent to query internal SQL, GitHub, Slack, Jira, documentation, and Kubernetes telemetry through 28 RBAC-gated MCP tools, with shared memory for playbook retrieval and incident workflows.

Aggregates tasks from multiple sources (Jira, Markdown TODO files, STM CLI) into a unified SQLite database with full-text search, tagging, and incremental sync capabilities.

Enables agents to interact with Salesforce, Atlassian (Jira/Confluence), and Supabase through standardized tools and resources. Provides both read-only access for querying data and write operations for managing records across these enterprise platforms.