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

@re-shell/mcp

v0.1.0

Published

Stdio MCP server exposing Re-Shell's read-only JSON commands as agent tools.

Readme

@re-shell/mcp

A Model Context Protocol (MCP) server that exposes Re-Shell's machine-readable commands to AI agents as typed, validated tools.

Re-Shell already emits a stable { ok, data, warnings } / { ok, error } envelope (the single source of truth lives in @re-shell/contracts). This server wraps the allow-listed, JSON-emitting commands so an MCP-capable agent can inspect and reason about a workspace safely — read-only by default, every result validated against the contract schema.

Tools

Read-only (always available):

| Tool | Wraps | Returns | |------|-------|---------| | workspace_summary | re-shell workspace summary --json | workspace overview envelope | | workspace_graph | re-shell workspace graph --json | dependency graph envelope | | workspace_health | re-shell workspace health --json | health summary envelope | | templates_list | re-shell templates list --json | template catalog | | templates_show | re-shell templates show <id> --json | one template | | templates_matrix | re-shell templates matrix --json | compatibility matrix | | doctor | re-shell doctor --json | diagnostics | | analyze | re-shell analyze --json | workspace analysis | | commands_list | re-shell commands list --json | command catalog |

Write tools (e.g. workspace_create) are only registered when RE_SHELL_MCP_ALLOW_WRITE=1 is set.

How it works

Each tool spawns the built Re-Shell CLI (spawn, no shell) with --json, parses stdout, and validates it against the matching @re-shell/contracts zod schema before returning it. A non-zero exit that still emits a valid error envelope is returned (so the agent sees the CLI's own code/message); non-JSON or schema-invalid output is surfaced as an MCP error.

Usage

# requires @re-shell/cli to be resolvable (installed, or RE_SHELL_BIN set)
npx @re-shell/mcp

Wire it into an MCP client (config excerpt):

{
  "mcpServers": {
    "re-shell": {
      "command": "npx",
      "args": ["-y", "@re-shell/mcp"],
      "env": { "RE_SHELL_BIN": "/abs/path/to/re-shell" }
    }
  }
}

| Env var | Purpose | |---------|---------| | RE_SHELL_BIN | Path to the re-shell binary (falls back to resolving @re-shell/cli) | | RE_SHELL_MCP_ALLOW_WRITE | Set to 1 to register mutating tools (off by default) |

Safety

  • Read-only by default — mutating tools require explicit opt-in.
  • No shell — commands run via spawn with an argv array, never shell: true.
  • Allow-listed — only the commands above are exposed (mirrors the dashboard hub's registry).
  • Contract-validated — every payload is checked against @re-shell/contracts before reaching the agent.