Labsco
1broseidon logo

Jira MCP Server

โ˜… 10

from 1broseidon

Integrates with Jira's REST API to manage issues programmatically.

๐Ÿ”ฅ๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedAccount requiredNeeds API keys

Jira MCP Server

smithery badge

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

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