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

mcpb-packager

v1.0.0

Published

Packaging automation tool for MCP servers as Desktop Extensions (.mcpb)

Readme

mcpb-packager

A command-line tool to automate the packaging of Model Context Protocol (MCP) servers into .mcpb Desktop Extensions. It can package local source directories, npm/PyPI packages launched on demand, or GitHub repositories cloned on the fly.

Installation

npm install -g mcpb-packager

Under the hood it uses @anthropic-ai/mcpb, which is installed automatically.

Prerequisites

  • Node.js ≥ 16 (always required)
  • git — only if you use --type http to clone repositories
  • uvx (from astral-sh/uv) — only if your end users will launch a Python MCP via --type uvx

Usage

Package an npm package (via npx)

mcpb-packager --package @energio/holded-mcp --type npx --env HOLDED_API_KEY

Use --env to declare the environment variables the end user will be prompted for when installing the extension.

Package a Python package (via uvx)

mcpb-packager --package trello-mcp-server --type uvx --env TRELLO_API_KEY

Package from a GitHub repository

The tool clones the repository, runs its install/build commands, and produces the bundle.

mcpb-packager --package https://github.com/user/repo-mcp.git --type http

Package a local MCP source directory

Drop an mcp-config.json next to your server and run from the parent directory:

mcpb-packager                  # scans cwd for any subdirectory with mcp-config.json
mcpb-packager ./my-local-mcp   # packages a specific local directory

Options

  • -p, --package <pkg> (Required for external packages) — npm package, PyPI package, or git URL.
  • -t, --type <type> (Required with --package) — execution strategy: npx, uvx, or http.
  • -e, --env <vars> (Optional) — comma-separated list of env variables the user will fill in (API_KEY,DB_HOST).
  • -a, --args <args> (Optional) — extra arguments passed through to the server when launched.
  • -o, --out <dir> (Optional) — output directory for generated .mcpb files. Defaults to the current working directory. Relative paths are resolved against the cwd.
  • -h, --help — show usage.

Output

By default the generated .mcpb files are written to the current working directory. Pass --out <dir> to redirect them somewhere else.

License

MIT