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

stacktree-install

v0.3.0

Published

Installer for stacktr.ee — wires the MCP server + Claude skill into your agent of choice.

Downloads

93

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

stevysmithstevysmith

Keywords

stacktreemcpclaudecursorcodexinstaller

Readme

stacktree-install

One-shot installer for stacktr.ee. Wires the MCP server (and the Claude /stacktree skill) into the agents you actually use.

npx stacktree-install

What it does

The CLI walks you through four prompts and then writes the relevant config files.

  1. Sign in. Pick one:
    • Open browser to sign in (default) — we open app.stacktr.ee/connect/cli with a one-time code, you sign in (Google / GitHub / email — sign-up is the same flow), confirm the code matches your terminal, and click Authorize. We mint a fresh API key bound to your account and the installer picks it up automatically. No copy-paste.
    • Paste an API key I already have — for anyone who already minted a key in the dashboard.
  2. Token storage. Inline in the MCP config (easiest), or via the STACKTREE_API_KEY environment variable.
  3. Install location. Current project (writes alongside your repo) or globally (writes to your home directory).
  4. Agents. Any subset of: Claude Code, Cursor, Codex, OpenCode, Amp.

For Claude, the installer also drops in the stacktree-publish skill so the agent knows when and how to ship HTML artifacts.

Skipping the prompts

Pass an existing key as a positional argument to skip the sign-in step entirely:

npx stacktree-install stk_live_xxxxxxxxxxxx

You'll still be asked the token-storage, location, and agents questions.

Where things land

| Agent | Config file | | ----------- | ------------------------------------------------------------ | | Claude Code | .mcp.json or ~/.claude.json, plus the skill at .claude/skills/stacktree-publish/ | | Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) | | Codex | ~/.codex/config.toml (global only) | | OpenCode | opencode.json or ~/.config/opencode/opencode.json | | Amp | ~/.config/amp/settings.json |

Existing servers and unrelated keys in those files are preserved — the installer merges its entry in.

Privacy & revocation

Browser-flow keys are minted on the server, labelled stacktree-install, and listed alongside any other keys at https://app.stacktr.ee/api-keys. Revoke any time from there.

Env vars

  • STACKTREE_API_URL — override the API base (defaults to https://api.stacktr.ee). Mostly useful for local dev.
  • STACKTREE_API_KEY — read at install time if you picked "env" token storage; thereafter the agent reads it from its own environment.