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

hyper-pm-mcp

v0.1.6

Published

stdio MCP server that runs the hyper-pm CLI

Readme

hyper-pm-mcp

stdio Model Context Protocol server that exposes the hyper-pm CLI to MCP hosts (for example Cursor or Claude Desktop).

Publishing to npm

Publish hyper-pm first, then this package. Use pnpm publish from each app directory (or --filter) so pnpm rewrites the workspace:^ range on hyper-pm to a real semver in the published manifest. Plain npm publish can leave workspace: specifiers intact and produce an uninstallable tarball.

Security

The hyper_pm_run tool runs the same hyper-pm process you would run locally with the given arguments. Only enable this server in MCP configurations you trust.

Build order

From the monorepo root:

  1. Build the CLI bundle: pnpm --filter hyper-pm build
  2. Build this server: pnpm --filter hyper-pm-mcp build

The server resolves the CLI at hyper-pm/dist/main.cjs via require.resolve("hyper-pm") (published packages use dist/index.cjs as the package entry; see @workspace/hyper-pm-cli-runner). Ensure hyper-pm is built so dist/main.cjs exists before starting the MCP server.

Environment

Optional variables are documented in env.example and parsed through @workspace/env. Notable:

  • HYPER_PM_CLI_PATH: absolute path to main.cjs when resolution from the workspace package is not sufficient.

Cursor MCP example

After building, point the host at the bundled ESM entry:

{
  "mcpServers": {
    "hyper-pm": {
      "command": "node",
      "args": ["/absolute/path/to/hyper-pm/apps/hyper-pm-mcp/dist/main.mjs"],
      "env": {}
    }
  }
}

Use the real absolute path to dist/main.mjs on your machine (or a pnpm exec / wrapper script that runs it).

Tool: hyper_pm_run

  • argv (required): CLI tokens after global options, e.g. ["epic", "read"] or ["doctor"].
  • Optional fields mirror hyper-pm globals: cwd, repo, tempDir, actor, githubRepo, dataBranch, remote, sync, keepWorktree.

--format json is always injected. The tool response is JSON text with exitCode, stdout, stderr, signal, and parsedStdout (when stdout is valid JSON).

Scripts

  • pnpm build — bundle to dist/main.mjs
  • pnpm test / pnpm test:coverage
  • pnpm check-types / pnpm lint