What is 1broseidon Mcp Jira Server

1broseidon_mcp-jira-server is a Model Context Protocol server that integrates with Jira’s REST API, enabling AI assistants to manage Jira issues programmatically.

Use cases

Use cases include automating the creation and management of Jira issues, integrating AI assistants to streamline project workflows, and enhancing team collaboration by programmatically handling issue updates and comments.

How to use

To use 1broseidon_mcp-jira-server, you need to set up a Jira account with API access, generate an API token, install the necessary dependencies, build the server, and configure it with your Jira credentials in a specific JSON format.

Key features

Key features include creating new issues (Tasks, Epics, Subtasks), listing issues with optional status filtering, updating existing issues, retrieving detailed issue information, deleting issues, and adding comments to issues.

Where to use

1broseidon_mcp-jira-server is primarily used in software development and project management environments where Jira is utilized for issue tracking and project organization.

Jira MCP Server

A Model Context Protocol server that provides integration with Jira’s REST API, allowing AI assistants to manage Jira issues programmatically.

Features

This server provides tools for managing Jira issues:

• Create new issues (Tasks, Epics, Subtasks)
• List issues with optional status filtering
• Update existing issues (summary, description, status)
• Get detailed issue information
• Delete issues
• Add comments to issues

Setup

Prerequisites

1. A Jira account with API access
2. Jira API token (can be generated from Atlassian Account Settings)

Installation

1. Install dependencies:

npm install

2. Build the server:

npm run build

Configuration

1. Create a .jira-config.json file in your working directory:

{
  "projectKey": "YOUR_PROJECT_KEY"
}

2. Configure the MCP server with your Jira credentials:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": [
        "/path/to/jira-server/build/index.js"
      ],
      "env": {
        "JIRA_EMAIL": "[email protected]",
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_DOMAIN": "your-domain"
      }
    }
  }
}

Available Tools

create_issue

Creates a new Jira issue

• Required parameters:
  • working_dir: Directory containing .jira-config.json
  • summary: Issue title
  • description: Issue description
  • type: Issue type (Task, Epic, or Subtask)

list_issues

Lists issues in the project

• Required parameters:
  • working_dir: Directory containing .jira-config.json
• Optional parameters:
  • status: Filter by status (e.g., “To Do”, “In Progress”, “Done”)

update_issue

Updates an existing issue

• Required parameters:
  • working_dir: Directory containing .jira-config.json
  • issue_key: Issue key (e.g., PRJ-123)
• Optional parameters:
  • summary: New title
  • description: New description
  • status: New status

get_issue

Gets detailed information about a specific issue

• Required parameters:
  • working_dir: Directory containing .jira-config.json
  • issue_key: Issue key (e.g., PRJ-123)

delete_issue

Deletes a Jira issue

• Required parameters:
  • working_dir: Directory containing .jira-config.json
  • issue_key: Issue key (e.g., PRJ-123)

add_comment

Adds a comment to an existing issue

• Required parameters:
  • working_dir: Directory containing .jira-config.json
  • issue_key: Issue key (e.g., PRJ-123)
  • comment: Comment text to add

Development

For development with auto-rebuild:

npm run watch

Error Handling

The server includes comprehensive error handling for:

• Invalid project keys
• Missing configuration
• Invalid issue types
• API authentication errors
• Invalid status transitions

Output Formatting

Issue information is formatted to include:

• Issue key and summary
• Issue type and status
• Creation date and creator
• Description
• Comments (if any) with author and timestamp