"Accessing Jira Tickets and Updating Their State" matching MCP servers:

A Model Context Protocol (MCP) server for GitLab and Jira integration. This server allows AI agents like gemini-cli to interact with your GitLab and Jira instances.

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

A Jira Server/Data Center MCP server for issue management, workflow analysis, and field discovery, using JQL and REST API v2 with PAT authentication.

Enables AI agents to manage self-hosted Atlassian Jira Server/Data Center issues and Bitbucket Server/Data Center repositories, pull requests, branches, commits, and files through MCP tools.

MCP server providing tools to read and write Jira Cloud issues, including a bridge to GitHub commits for tracing issues to code.

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.

Enables seamless integration with GitLab and Jira Server/Data Center via MCP, using Bearer token authentication and REST API v2, supporting both on-premise instances.

Enables end-to-end automation of developer workflows from Jira issue tracking to GitHub pull requests through natural language, allowing developers to search issues, create branches, commit changes, and manage PRs directly from their IDE.

A modular MCP server integrating Jira and GitHub to automate developer workflows, enabling AI agents to manage issues, branches, commits, and pull requests directly from the 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 read-only access to GitLab and Jira data through MCP, allowing users to list projects, merge requests, issues, and search Jira tickets via natural language queries. Provides safe, structured access to project management data without write permissions.

A read-only MCP server that securely serves Jira (Server/Data Center) data to Claude Code without exposing the personal access token, with optional GitLab integration.

This MCP server connects GitLab projects and merge requests with Jira work tracking, Confluence pages, and Grafana dashboards. It provides read-only access to GitLab, Confluence, and Grafana, while Jira mutations require explicit confirmation.

Enables secure integration between GitHub and Jira with permission controls, allowing users to manage repositories, create issues and pull requests, and handle Jira project workflows through natural language. Supports OAuth authentication and comprehensive security enforcement for both platforms.

A FastMCP-based server designed for the banking and fintech domains, providing tools for database queries, Git operations, and deployment management. It features a modular architecture with reusable prompt templates and integrated security practices for sensitive data handling.

Enables searching GitHub users and repositories, fetching details, and performing stock market technical analysis via AlphaVantage.

Enables AI assistants to draft content such as PR descriptions, tickets, or messages, with a review window for live preview, editing, and approval before submission.

A deterministic MCP server that reimplements ai-git-fish workflows (aicommit, aibranch, aipr) with Leantime integration, enabling Claude Code and Codex to perform git operations and manage tickets without an internal LLM.

Enables validation of commit messages, branch names, author info, push safety, and repository state using commit-check rules, accessible as MCP tools.

MCP server that acts as a thin proxy over GitLab REST API v4, enabling users to list merge requests, view diffs, and leave inline comments without leaving their MCP client.

Local code review for people and their coding agents: an agent opens a review of its changes and hands over a link, the person comments on lines, and the agent reads the threads, replies and resolves what it fixed. Reads the git worktree directly, uncommitted work included; nothing leaves the machine.

Generates daily standup drafts from your actual GitHub, Jira, Linear, and Slack activity, grouping work items and detecting blockers.

A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, allowing users to query work items with plans to support creating/updating items, managing pipelines, handling pull requests, and administering sprints and branch policies.

Provides fresh project context to coding agents by combining Markdown documentation and live Git state, enabling deterministic startup briefs and bounded document retrieval for MCP-compatible tools.

An MCP server for reviewing Bitbucket Cloud pull requests, allowing clients to read PRs, tickets, and comments and leave review comments without leaving the editor.

Enables searching and retrieving GitHub portfolio repositories and their READMEs through natural language.

Provides AI agents with persistent, branch-aware context memory by storing summaries per Git branch and automatically enriching them with recent commits and divergence from main. Enables agents to maintain coherent state across sessions without mixing contexts from different branches.

Enables AI assistants to browse, search, and retrieve source code of 129 VengeanceUI components from their GitHub repository.

Local-first dev memory: indexes Git commits, PRs, Jira/Linear tickets, Confluence docs, Slack threads, and Calendar events into a local SQLite/FTS5/ONNX index, and exposes them as MCP tools so Claude Code, Cursor, and Codex can search and cite your past work.