Jira

Provides MCP-based access to JIRA data and actions like search, create/update, clone, comment, and work logging.

python

0

GitHub Stars

python

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "klauseduard-vibe-coded-jira-mcp": {
      "command": "./run-jira-mcp.sh",
      "args": [],
      "env": {
        "JIRA_URL": "https://your-jira-instance.atlassian.net",
        "JIRA_USERNAME": "your_email@example.com",
        "JIRA_API_TOKEN": "YOUR_API_TOKEN"
      }
    }
  }
}

You can connect AI coding assistants to your JIRA data using this MCP server, letting you search, create, update, comment on, clone, and log work on issues directly from your AI workflows. It provides a stable bridge between your JIRA instance and client tools so you can automate common project-tracking tasks with confidence.

How to use

You interact with the MCP server through an MCP client. Start by ensuring your JIRA connection details are available through environment variables. Then, within your AI workflow, perform common actions such as searching for issues with JQL, retrieving issue details, creating or updating issues, adding comments, cloning issues to work around field constraints, and logging work time. The server exposes these capabilities as MCP operations that your assistant can invoke in a consistent way.

How to install

Prerequisites: you need Python and the ability to install Python packages. A terminal with basic shell access is required.

python3 -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
pip install -r requirements.txt

Configure your JIRA connection by creating a .env file with your credentials and URL.

JIRA_URL=https://your-jira-instance.atlassian.net
JIRA_USERNAME=your_email@example.com
JIRA_API_TOKEN=your_api_token

Start the MCP server using the provided start script.

./run-jira-mcp.sh

Configuration and security

Environment variables control how the server connects to JIRA. Keep the .env file secure and do not commit it to version control. Use HTTPS for your JIRA instance and API tokens for authentication.

Recommended protections include rotating API tokens regularly, auditing access to your credentials, and choosing the least-privilege permissions necessary for your automation tasks.

Notes and tips

The server supports common MCP workflows such as searching with JQL, selecting field views, creating and updating issues, cloning issues to handle complex configurations, adding comments, and logging work time. If you need to work around heavy customizations in JIRA, cloning can be a useful approach, though it may have limitations in some environments.

Troubleshooting

If the server fails to start, verify that the environment file is present and correctly formatted, the required Python packages are installed, and the JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN are valid. Check logs for authentication errors, network connectivity, and permission issues in JIRA.

Available tools

get_issue

Retrieve details for a specific JIRA issue by key.

search_issues

Execute a JQL query to find issues matching complex criteria.

create_update_issue

Create a new JIRA issue or update an existing one with specified fields.

add_comment

Add a comment to a specified JIRA issue.

clone_issue

Create a clone of an existing issue, optionally changing project or fields for handling custom requirements.

log_work

Log work time against a JIRA issue.