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

@zswarm/pi

v0.1.4

Published

Bridge stdio MCP servers into pi as native tools

Downloads

679

Readme

@zswarm/pi

Bridge stdio MCP servers into pi as native tools. Defaults to zSwarm; point it at any stdio MCP server with ZSWARM_MCP_SERVERS.

Install

pi install npm:@zswarm/pi

From a checkout of this repo:

pi install -l ./packages/pi

-l installs into the project (.pi/settings.json) rather than your home directory, and is shareable — pi installs it for anyone who opens the project.

Restart pi after installing. After that /reload is enough, since the extension registers on every bind. On success:

[Extensions]
  zswarm-mcp.ts
 MCP zswarm: 1 tool(s) registered

Configure

With nothing set, it looks for zSwarm's own server in the only two places it can be, in order:

  1. <cwd>/bin/launch-mcp.mjs — a checkout of the zswarm repo, pi started at its root
  2. @zswarm/mcp — resolved by name, wherever your package manager put it

@zswarm/mcp is a dependency of this package, so a plain pi install npm:@zswarm/pi pulls the server in and step 2 finds it. Nothing to configure.

Found in neither, it registers nothing and says so. It does not guess a relative path: a wrong guess becomes a spawn error you have to decode, whereas finding nothing names the variable that fixes it.

Set ZSWARM_MCP_SERVERS to bridge a different server — JSON, same shape as other MCP hosts:

ZSWARM_MCP_SERVERS='{
  "zswarm": {"command": "/abs/path/to/node", "args": ["/abs/path/to/launch-mcp.mjs"]},
  "other":  {"command": "/abs/path/to/other-server"}
}'

Use absolute paths throughout. Hosts that spawn servers outside your shell inherit no PATH, so a bare node fails with exec: "node": executable file not found in $PATH. The built-in defaults use process.execPath — the interpreter already running pi — for exactly this reason.

Tools register as <server>_<tool>, or <tool> when the names match. A failed server is skipped. Set ZSWARM_SESSION if more than one Zellij session is live.

How it works

On load: spawn each server → initializetools/listpi.registerTool(). A call is tools/call. JSON-RPC, no SDK; schemas pass through as-is. Tools may not be ready in the same instant pi starts.

License

MIT