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

@jam-mcp/bootstrap

v1.8.0

Published

Zero-install entry point for JAM (Jira Agent MCP) - first-run setup for humans and coding agents

Readme

@jam-mcp/bootstrap

The zero-install way into JAM (Jira Agent MCP).

This package exists so the first command a person or a coding agent runs needs nothing installed beforehand:

npx --yes @jam-mcp/[email protected] init          # for a person
npx --yes @jam-mcp/[email protected] setup --agent # for a coding agent, JSON only

init chooses how JAM runs on this machine and wires up the current project. setup --agent detects, plans, applies what is safe, and verifies — stopping only where a person is genuinely required (choosing a Jira project, authenticating).

What it is, and is not

It is an end-user entry point, but it holds no setup logic of its own. It depends on @jam-mcp/server at an exact version and forwards to the same commands JAM's own CLI would run; anything other than init is passed through unchanged. Any decision made here would be a second implementation to keep in sync with the setup core.

That pass-through is also why bootstrap is what JAM names in machine-readable instructions. On a machine that has just met JAM there is no global command to call and no configured runtime for the launcher to dispatch to — bootstrap needs neither, so npx --yes @jam-mcp/[email protected] <anything> works when nothing else does.

The three packages divide up like this:

| Package | Role | |---|---| | @jam-mcp/bootstrap | first run and recovery — needs nothing installed | | @jam-mcp/launcher | what a coding agent registers; resolves which JAM build runs | | @jam-mcp/server | JAM itself: MCP tools, setup core, CLI |

Day to day you don't need this package: your coding agent launches the launcher, and if you installed the launcher globally you have jam too.

More