"Permission requirements to create and edit issues in Jira using MCP" matching MCP servers:

Enables LLMs to list, create, and comment on GitHub issues using your own GitHub identity via stdio transport.

Lets agents read a GitHub repository's live issues through read-only tools for listing, filtering, fetching details with comments and cross-references, searching, and exploring labels and milestones, with transparent pagination and provenance notes.

Enables triage of GitHub issues by fetching and filtering issues, checking claim status, and listing new open issues across a watch-list.

Enables AI agents to manage GitHub issues by listing, creating, searching, and commenting on them through MCP.

A standalone MCP server that exposes a narrow set of GitHub Issues tools for a single repository, securely handling a GitHub personal access token so agents never see the credential.

Exposes GitHub issue operations as tools for LLM agents, enabling listing, creating, commenting on, closing, and searching issues via natural language.

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 assistants to discover, filter, and triage GitHub issues across repositories, with tools for fetching issue details, listing issues by state/labels, and finding related pull requests.

Provides comprehensive file system operations including reading, writing, searching, patching, code analysis, SSH transfers, and git operations, while aiming to reduce token usage in Claude Desktop.

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

A modular monolith MCP server connecting multiple providers (Redash, PostgreSQL, GitHub) with unified permission, security, and auditing, enabling secure data access and tool execution.

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.

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.

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.

An MCP server that enables AI agents to retrieve detailed GitHub Pull Request information using git commit hashes, branch names, or PR numbers. It automatically detects repositories and extracts comprehensive PR data including descriptions, labels, and reviews via the GitHub CLI.

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