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

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

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

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

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.

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.

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.

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

Enables querying any GitHub, GitLab, or Bitbucket repository and getting AI-generated answers about the codebase, powered by Gemini.

Enables asking natural-language questions about any GitHub repository and receiving answers grounded in the actual code, with read-only enforcement and automatic repository fetching.

Semantic git queries via MCP. Beyond git log — answer who/what/why about any line, file, or branch with blame, co-change, PR linkage.

Enables natural-language queries about public GitHub repositories, including issues, pull requests, repo metadata, and READMEs, via the GitHub API.

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

Fetches glasz-style spec files (product.md, tech.md, test-plan.md, and INDEX.md) from GitHub repositories, enabling LLMs to answer questions about features, stories, and acceptance criteria without cloning or pasting files.

Odds are, most of what you want to build is already open source. Tell your AI agent what you're making, and it finds it: which repos to use as they are, which to adapt, and what's left for you to write. Every repo it names is real, licensed for your use or flagged, and checked live.

An MCP (Model Context Protocol) server for handling GitHub URLs with validation and parsing capabilities. This server provides tools to convert between GitHub repository information and URLs, with intelligent validation to distinguish between public repositories, private repositories, and non-exist