npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rui.branco/jira-mcp

v1.6.12

Published

Jira MCP server for Claude Code - fetch tickets, search with JQL, update tickets, manage comments, change status, and get Figma designs

Readme

Jira MCP Server

A Model Context Protocol (MCP) server that brings Jira ticket context directly into Claude Code. Fetch complete ticket information including descriptions, comments, attachments, and linked Figma designs without leaving your development environment.

Overview

When working on development tasks, context switching between Jira and your code editor breaks flow and wastes time. This MCP server solves that by:

  • Fetching complete ticket context - Get descriptions, comments, status, and metadata instantly
  • Downloading attachments - Image attachments are downloaded and displayed inline
  • Auto-fetching Figma designs - Linked Figma URLs are automatically detected and exported as images
  • Enabling natural queries - Search tickets with JQL directly from Claude Code

Features

| Feature | Description | |---------|-------------| | Full Ticket Details | Summary, description, status, priority, assignee, reporter, sprint, parent | | Comments | All comments with author and timestamp | | Attachments | Auto-download image attachments (PNG, JPG, GIF, WebP) | | Linked Issues | View related tickets and their relationships | | Figma Integration | Auto-detect and export Figma designs linked in tickets | | JQL Search | Search across your Jira instance with powerful queries |

Installation

Prerequisites

  • Node.js 18+
  • Claude Code CLI
  • Jira Cloud account with API access

Step 1: Add to Claude Code

claude mcp add --transport stdio jira -- npx -y @rui.branco/jira-mcp

Step 2: Get Your Jira API Token

  1. Go to Atlassian API Tokens
  2. Click "Create API token"
  3. Enter a label (e.g., "Claude Code MCP")
  4. Click "Create"
  5. Copy the token (you won't be able to see it again)

Step 3: Configure Credentials

Run the setup with your credentials:

npx @rui.branco/jira-mcp setup "[email protected]" "YOUR_API_TOKEN" "https://company.atlassian.net"

| Parameter | Description | Example | |-----------|-------------|---------| | Email | Your Atlassian account email | [email protected] | | API Token | The token you created in Step 2 | ATATT3xFfGF0... | | Base URL | Your Jira instance URL | https://company.atlassian.net |

Or run interactively (will prompt for each value):

npx @rui.branco/jira-mcp setup

Step 4: Verify

Restart Claude Code and run /mcp to verify the server is connected.

Alternative: Manual Installation

If you prefer to install manually:

git clone https://github.com/rui-branco/jira-mcp.git ~/.config/jira-mcp
cd ~/.config/jira-mcp && npm install
node setup.js

Then add to Claude Code:

claude mcp add --transport stdio jira -- node $HOME/.config/jira-mcp/index.js

Usage

Fetch a Ticket

> Get ticket PROJ-123

# Returns full ticket with description, comments, attachments, and Figma designs

Search Tickets

> Search for my open tickets

# Uses JQL: assignee = currentUser() AND status != Done

Add Comments with Mentions

Use @FirstName LastName syntax to mention users in comments:

> Add a comment to PROJ-123: "@John Doe Please review this implementation"

# The mention is automatically resolved and the user gets notified

Example Output

# PROJ-123: Implement user authentication

Status: In Progress | Type: Story | Priority: High
Assignee: John Doe | Reporter: Jane Smith

## Description
Implement OAuth2 authentication flow...

## Comments (2)
### Jane Smith - Jan 15, 2025
Please ensure we support Google SSO...

## Attachments (1)
- mockup.png (image/png, 245KB)
  [Image displayed inline]

## Figma Designs (1)
### Auth Flow Design - Login Screen
- Exported 3 image(s):
  - Login Form: ~/.config/figma-mcp/exports/...
  - Error States: ~/.config/figma-mcp/exports/...
  - Success State: ~/.config/figma-mcp/exports/...

Figma Integration

This MCP automatically detects Figma URLs in ticket descriptions and comments. When figma-mcp is configured:

  • Figma links are automatically fetched
  • Large frames are split into sections for better readability
  • Images are exported at 2x scale for clarity
  • All images are displayed inline in Claude Code

To enable Figma integration:

  1. Install and configure figma-mcp
  2. Restart Claude Code
  3. Figma links will be auto-fetched when you get a ticket

API Reference

Tools

| Tool | Description | Parameters | |------|-------------|------------| | jira_get_myself | Get the current authenticated user's accountId and info (use for assigning tickets) | none | | jira_get_ticket | Fetch a ticket by key with description, comments, attachments, and Figma designs | issueKey (required), downloadImages, fetchFigma | | jira_search | Search tickets using JQL | jql (required), maxResults | | jira_add_comment | Add a comment to a ticket (supports @mentions) | issueKey (required), comment (required) | | jira_reply_comment | Reply to a specific comment with quote and mention | issueKey (required), commentId (required), reply (required) | | jira_edit_comment | Edit an existing comment (supports @mentions) | issueKey (required), commentId (required), comment (required) | | jira_delete_comment | Delete a comment (irreversible) | issueKey (required), commentId (required) | | jira_transition | Change ticket status by name or ID (auto-handles intermediate steps) | issueKey (required), targetStatus or transitionId | | jira_update_ticket | Update ticket fields (summary, description, assignee, priority, labels) | issueKey (required), plus optional field parameters |

Configuration

Config stored at ~/.config/jira-mcp/config.json:

{
  "email": "[email protected]",
  "token": "YOUR_API_TOKEN",
  "baseUrl": "https://company.atlassian.net"
}

Error Handling

The server provides clear error messages:

| Error | Meaning | |-------|---------| | Figma API rate limit exceeded | Too many Figma requests, wait a few minutes | | Figma access denied | Check Figma token or file permissions | | Figma not configured | Install and configure figma-mcp |

Security

  • API tokens are stored locally in ~/.config/jira-mcp/config.json
  • Config files are excluded from git via .gitignore
  • Tokens are never logged or transmitted except to Jira/Figma APIs
  • Attachments are downloaded to ~/.config/jira-mcp/attachments/

License

MIT

Related