Jira Connector Service Module

This Simple Model Context Protocol (MCP) service establishes a bridge for autonomous agents to interface with Atlassian Jira instances. Its capabilities allow for programmatic execution of critical actions, such as: - Retrieving the inventory of tasks allocated to the authenticated user. - Inserting supplementary remarks or annotations onto specific issues. - Querying the permissible state transitions for a given ticket. - Enforcing transitions to update an issue's current status.

Prerequisites for Deployment

To successfully deploy and operate this component, the following prerequisites must be satisfied:

• Operational Docker engine.
• A valid Jira credential set possessing necessary API interaction privileges.
• Correct provisioning of configuration parameters via environment variables (detailed below).

Essential Environment Configuration

Populate a .env file within the primary working directory with the subsequent configuration settings:

JIRA_SERVER=https://yourcompany.atlassian.net JIRA_USERNAME=your.identifier@yourcompany.com JIRA_API_KEY=your_secret_token JIRA_PROJECT_KEY=PROJKEY

API token acquisition location: https://id.atlassian.com/manage-profile/security/api-tokens

Local Execution Pathways

Method A: Containerized Deployment

Execute the following shell commands:

bash

Grant execution rights and launch via Docker

chmod +x launch_via_container.sh ./launch_via_container.sh

Method B: Direct Python Execution

1. Install all necessary package dependencies:

bash pip install -r requirements.txt

1. Initiate the application server:

bash uvicorn src.server:app --reload

This action commences service hosting, typically accessible at http://localhost:8000.

Accessing the MCP Interface

The functional endpoint for this MCP service is located at http://localhost:8000/mcp.