Jira

by guanghuang

Not rated
GitHub

About

Interact with Jira to manage issues, projects, and workflows using the Jira Cloud Platform REST API.

Details

Author
guanghuang
Categories
Productivity, Project Management, Automation

Setup

Install Jira in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/guanghuang/jira-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

This Model Context Protocol (MCP) server enables Large Language Models (LLMs) to interact with Jira through a standardized API. It allows AI assistants to perform common Jira operations without requiring direct API integration, making it easier to build AI-powered tools that work with your Jira instance.

- Jira Platform API Integration: Comprehensive access to Jira Cloud Platform REST API
- Jira Software API Integration: Work with Jira Software features like boards, sprints, and epics
- MCP Protocol Support: Standardized interface for AI assistants and automation tools
- Authentication: Basic auth support using Atlassian PAT (Personal Access Token)

The MCP server supports the following Jira operations:

- get_all_agile_boards: Retrieve all available agile boards
- get_epics_from_board: Get all epics associated with a specific board
- get_issues_from_board: Get all issues from a specified board
- get_issues_from_epic: Retrieve all issues associated with a specific epic
- get_issues_from_sprint: Get all issues from a specified sprint
- get_sprints_from_board: Retrieve all sprints associated with a board
- move_issues_to_epic: Move specified issues under an epic

- add_jira_comment: Add a comment to a Jira issue
- create_issue: Create a new Jira issue
- delete_issue: Delete an existing Jira issue
- get_issue: Retrieve details of a specific issue
- get_issue_fields: Get all available fields for issues
- get_issue_transitions: Get possible status transitions for an issue
- get_project_versions: Get all versions in a project with pagination support
- search_issue_by_jql: Search for issues using JQL (Jira Query Language)
- transition_jira_issue: Change the status of an issue
- update_issue: Update the details of an existing issue
- add_jira_attachments: add attachments to an existing issue

- search_user: Find Jira users based on search criteria
- get_myself_info: Get information about the authenticated user

docker run -d --name jira-mcp \ -p 8080:8080 \ -e atlassian.url=https://your-company.atlassian.net \ -e atlassian.username=your-jira-email \ -e atlassian.pat=your-jira-pat \ guang1/jira-mcp:latest

Create a configuration file (e.g.,atlassian.config):

atlassian.url=https://your-company.atlassian.net atlassian.username=your-jira-email atlassian.pat=your-jira-pat
docker run -d --name jira-mcp \ -p 8080:8080 \ --env-file atlassian.config \ guang1/jira-mcp:latest
services: jira: container_name: jira-mcp image: guang1/jira-mcp environment: - atlassian.url=https://your-company.atlassian.net - atlassian.username=your-jira-email - atlassian.pat=your-jira-pat ports: - "8080:8080" restart: always
services: jira: container_name: jira-mcp image: guang1/jira-mcp env_file: - jira.config ports: - "8080:8080" restart: always

Mustpassquarkus.mcp.server.stdio.enabled=true,quarkus.log.console.enable=falseandquarkus.log.console.stderr=falseenvironment variables with-iinteractive option.

docker run --rm \ -e atlassian.url=https://your-company.atlassian.net \ -e atlassian.username=your-jira-email \ -e atlassian.pat=your-jira-pat \ -e quarkus.mcp.server.stdio.enabled=true \ -e quarkus.log.console.enable=false \ -e quarkus.log.console.stderr=false \ -i guang1/jira-mcp:latest
docker run --rm --env-file=atlassian.config \ -e quarkus.mcp.server.stdio.enabled=true \ -e quarkus.log.console.enable=false \ -e quarkus.log.console.stderr=false \ -i guang1/jira-mcp:latest

To use the Docker version with Claude Desktop, add this to yourclaude_desktop_config.jsonorserver_config.jsonfile:

{ "mcpServers": { "jira": { "command": "docker", "args": [ "run", "--rm", "-e", "atlassian.url=https://your-company.atlassian.net", "-e", "atlassian.username=your-jira-email", "-e", "atlassian.pat=your-jira-pat", "-e", "quarkus.log.console.enable=false", "-e", "quarkus.log.console.stderr=false", "-i", "guang1/jira-mcp:latest" ] } } }
{ "mcpServers": { "jira": { "command": "docker", "args": [ "run", "--rm", "--env-file=atlassian.conf", "-e", "quarkus.mcp.server.stdio.enabled=true", "-e", "quarkus.log.console.enable=false", "-e", "quarkus.log.console.stderr=false", "-i", "guang1/jira-mcp:latest" ] } } }

To generate a Personal Access Token for Jira:
- Go tohttps://id.atlassian.com/manage-profile/security/api-tokens
- Click "Create API token"
- Give your token a name (e.g., "MCP Server")
- Copy the generated token for use with this MCP server

⚠️Warning: This MCP server requires authentication credentials with access to your Jira instance. Consider the following security practices:

- Create a dedicated Jira service account with appropriate permissions
- Regularly rotate your API token
- Run the container in a secure, isolated environment
- Use network security rules to restrict access to the MCP server
- Be cautious about which operations you allow LLMs to perform

-

Set a Default Ticket Prefix
Define a default ticket prefix in your rules (e.g.,MyProj-). This allows you to reference tickets in chat by number only (e.g.,1234instead ofMyProj-1234).

Configure Personal Jira Account ID
Specify your Jira account ID in the rules to avoid repeated API calls (such asget_myself_info) for every operation.

Customize Jira Fields
Set custom fields (e.g., story points, developer, etc.) in your rules to prevent the AI from callingget_issue_fieldseach time.

Automate Issue Management
Create and update Jira issues automatically based on natural language requests.

Generate Reports and Summaries
Produce Jira reports and summaries on demand.

Sprint Planning and Epic Management
Assist with sprint planning and epic management tasks.

Conversational Jira Interaction
Enable team members to interact with Jira using natural, conversational language.

- Verify your API token has the required permissions
- Check that your atlassian URL is correct and accessible
- Ensure your atlassian username (email) is correct
- Check container logs for detailed error information

This project is licensed under the MIT License - see the LICENSE file for details.

An MCP server for interacting with the Jira API to manage projects, issues, and workflows.

About AI-powered Jira CLI and MCP server for humans and agents manage issues, sprints, boards with interactive wizards, multi-provider AI

An MCP server for managing Tempo worklogs in Jira. It connects to Jira and Tempo services using API tokens and environment variables.

Keep teams & agents coordinated automatically

Connect to the Taskade platform via MCP. Access tasks, projects, workflows, and AI agents in real-time through a unified workspace and API.

Interact with Atlassian tools like Confluence and Jira.

Integrates AI with Atlassian Jira to manage projects, search for issues, and view development information like commits and pull requests.

The Outcome Backcasting MCP is a strategic planning tool that helps you work backwards from a desired future outcome to identify the specific steps, resources, and dependencies needed to achieve your goals. Unlike traditional forward planning, backcasting starts with your end goal and creates a reverse roadmap to get there.

Interact with the ClickUp API to manage tasks, lists, and spaces, automating project planning and workflows.

Apify-hosted MCP server for ClickUp with 20 tools. Tasks, spaces, folders, lists, views, docs, and custom fields. No local setup needed.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.