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

@tocharianou/jira-mcp

v1.0.0

Published

Jira MCP Server – issue search, create, update, comment, status transitions, and project listing for security incident management

Readme

Jira MCP Server

npm version License: Apache-2.0 Node.js >= 18

A Model Context Protocol (MCP) server for Jira — issue search, creation, updates, comments, status transitions, and project listing. Purpose-built for security incident management and SOC workflows.

Quick Start

Claude Desktop (stdio)

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "@tocharianou/jira-mcp"],
      "env": {
        "JIRA_HOST": "https://yourorg.atlassian.net",
        "JIRA_EMAIL": "[email protected]",
        "JIRA_TOKEN": "<your-api-token>"
      }
    }
  }
}

Get your Jira API token at id.atlassian.com/manage-profile/security/api-tokens.

HTTP / Streamable mode

MCP_TRANSPORT=http MCP_HTTP_PORT=3002 JIRA_HOST=https://yourorg.atlassian.net [email protected] JIRA_TOKEN=<token> npx @tocharianou/jira-mcp

Then point your MCP client at http://localhost:3002/mcp.

Features

  • Issue search — JQL-powered queries for incidents, vulnerabilities, and tasks
  • Issue management — create, update, comment, and transition issues
  • Incident tracking — open security tickets directly from investigation findings
  • Project discovery — list all accessible Jira projects
  • Token limiting — built-in MAX_TOKEN_CALL guard prevents context overflow

Configuration

| Environment variable | Required | Description | |---|---|---| | JIRA_HOST | ✓ | Jira Cloud: https://yourorg.atlassian.net / Server: https://jira.company.com | | JIRA_EMAIL | ✓* | Atlassian account email (Cloud only; leave empty for Server/DC) | | JIRA_TOKEN | ✓ | API token (Cloud) or Personal Access Token (Server/Data Center) | | JIRA_API_VERSION | – | 3 for Cloud (default), 2 for Server/Data Center | | JIRA_VERIFY_SSL | – | true/false (default: true) | | MAX_TOKEN_CALL | – | Token limit per tool response (default: 20000) | | MCP_TRANSPORT | – | stdio (default) or http | | MCP_HTTP_PORT | – | HTTP server port (default: 3002) | | MCP_HTTP_HOST | – | HTTP server host (default: localhost) |

* JIRA_EMAIL is required for Jira Cloud. Leave empty for Jira Server / Data Center (use PAT only).

Available Tools

| Tool | Description | |------|-------------| | jira_health_check | Test connection, verify account info and server version | | search_issues | Search issues using JQL — find incidents, open vulnerabilities, remediation tasks | | get_issue | Get full details of a single issue including comments and history | | create_issue | Create a new issue (incident, task, bug, etc.) | | update_issue | Update summary, description, priority, or labels | | add_comment | Add a comment to record investigation findings | | list_transitions | List available status transitions for an issue | | transition_issue | Move an issue to a new status (e.g. In Progress, Resolved, Closed) | | list_projects | List all accessible Jira projects with keys and types |

Example Queries

  • "Search for all open critical security incidents in the SEC project"
  • "Create a Jira ticket for the suspicious login activity from 192.168.1.100"
  • "Get the full details of ticket SEC-1234 including all comments"
  • "Move SEC-1234 to Resolved and add a closing comment with my findings"
  • "List all Jira projects I have access to"

Debugging

Use the MCP Inspector to test and debug:

npm run inspector

Server logs are written to stderr so they do not interfere with the MCP JSON-RPC stream on stdout.

Troubleshooting

| Symptom | Likely cause | |---------|-------------| | 401 Unauthorized | Invalid JIRA_TOKEN or wrong JIRA_EMAIL | | 403 Forbidden | Insufficient permissions on the project | | 404 Not Found | Issue key or project does not exist | | ECONNREFUSED | Wrong JIRA_HOST or Jira server not reachable | | SSL errors | Set JIRA_VERIFY_SSL=false for self-signed certs (Server/DC only) | | Token limit exceeded | Reduce max_results or set break_token_rule: true |

Development

git clone https://github.com/TocharianOU/jira-mcp.git
cd jira-mcp
npm install --ignore-scripts
npm run build
cp .env.example .env   # fill in your credentials
npm start

Release

See RELEASE.md for the full release process.

License

Apache 2.0 — Copyright © 2024 TocharianOU Contributors