"A server for finding a Jira integration" matching MCP servers:

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

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

Codebase Q&A agent with git-history awareness. Explore a repo with list_files, read_file, and search, plus git log, blame, and diff and a repo map to answer "why did this change?" questions. Runs locally as an MCP server for Claude Code and other MCP clients.

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.

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.

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 AI agents to interact with GitHub through OAuth-authenticated operations including starting authorization flows, listing repositories, and creating issues using stored access tokens.

Enables automated GitHub issue querying and repository tool actions through natural language, powered by Groq Llama-3 and the GitHub REST API.

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.

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.

Enables Codex and other MCP clients to read kickoff cards, acceptance criteria, Git evidence, and next steps, then append validated, audited progress events for resumable project handoffs.

Zero-dependency stdio MCP server for token-aware prompt version diffs. Compare prompts or files and get machine-readable token delta reports with confidence labels.

Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.

Self-hosted MCP coding server and unified local Control Center for ChatGPT web, enabling file editing, command execution, Git operations, and optional upstream MCP tools with conversation access controls.

Enables Codex agents to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail and next step, then append validated, audited, idempotent progress events that become matching project-record Git commits. Access is scoped to one workspace and project through short-lived, revocable, hash-stored credentials that cannot touch members, keys, deletion, publication or deployment.

It enables AI agents to retrieve Git-backed project context, handoff packages, and next actions, then append validated, audited progress events as project-record commits.

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.

Extracts diffs from GitHub Pull Requests, allowing users to retrieve and analyze changes between branches in a repository.

It lets AI coding clients read a project’s kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, then append a validated, audited, idempotent progress event with a matching project-record Git commit.

Enables Codex to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events with a matching Git commit.

Enables AI agents and humans to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step, then append audited, idempotent progress events that are committed to the project's Git record. Access is scoped per project through short-lived, revocable credentials, keeping high-risk actions outside the tool surface for human approval.

Enables users to safely read, write, edit, create directories, and list trees within a structured local Windows environment, with strict path validation and Git-based undo/version control.

Enables Codex projects to read Git-backed context, acceptance criteria, progress, and handoff packages, and to append validated, audited progress events with matching project-record commits.

Enables Codex users to retrieve Git-backed project context and append validated, audited progress events as matching Git commits, so work can resume safely across sessions.

Enables Codex agents to read a project's context — kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step — over MCP, and to append one validated, audited, idempotent progress event that is committed to a Git-backed project record using scoped, short-lived credentials.