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

@moor-sh/cli

v0.5.0

Published

Command-line interface for moor - manage your moor server's projects, logs, env vars, and container lifecycle.

Readme

@moor-sh/cli

Command-line interface for moor - manage your moor server's projects, logs, env vars, and container lifecycle from a terminal. Ships a moor binary.

Requires Bun on the machine running the CLI.

Install

One-shot (no install):

bunx @moor-sh/cli status

Global install (puts moor on PATH):

bun add -g @moor-sh/cli
moor status

Don't use bunx moor (without the scope) - moor on npm is an unrelated package.

Configure

export MOOR_URL=https://moor.example.com   # or http://127.0.0.1:8080 via SSH tunnel
export MOOR_API_KEY=your-api-key

MOOR_API_KEY grants admin-equivalent control of the moor host. See the self-hosting guide for how to generate and rotate it.

For a remote moor with private admin (the default), open an SSH tunnel from your laptop before running CLI commands:

ssh -L 8080:127.0.0.1:3000 your-server
export MOOR_URL=http://127.0.0.1:8080

Commands

moor status                          # list all projects
moor logs <project> [-f] [-n 100]    # view container logs
moor rebuild <project>               # rebuild from source
moor restart <project>               # stop + start
moor exec <project> <command>        # run a command in the container
moor env list <project>              # list environment variables
moor env set <project> KEY=VALUE     # set environment variables and restart
moor stats                           # server resource usage
moor mcp config --client <name>      # generate MCP client config snippet

moor mcp config

Generates a ready-to-paste config snippet for an MCP-compatible AI client. Removes the "open a doc, copy a JSON block, fill in the blanks" step from MCP setup.

moor mcp config --client claude        # or --client claude-code (alias)
moor mcp config --client codex

Output is JSON for claude / claude-code and TOML for codex. Prints to stdout - redirect or paste into ~/.claude.json or ~/.codex/config.toml. Optional flags: --url <url> (default http://127.0.0.1:8080), --api-key <key> (else read from MOOR_API_KEY env, then cwd .env, then a placeholder).

See @moor-sh/mcp for the MCP server itself.

Links

License

MIT.