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

whytree-mcp

v0.1.0

Published

MCP server that turns vague requests into purpose-driven structured briefs

Readme

Why Tree

Why Tree is a Claude Code skill for turning vague requests into purpose-driven briefs.

If a user starts with something fuzzy like:

  • "논문 쓸 거야"
  • "서비스 방향 정리해야 해"
  • "발표자료 만들어야 해"
  • "I need to figure out what this project is really trying to achieve"

Why Tree helps structure it into:

  • task
  • purpose
  • why now
  • problem framing
  • constraints
  • success signals
  • open questions
  • next-step options

The goal is simple: do not jump straight from a vague idea to shallow execution.

Install as a Claude Code skill

One-line install

git clone https://github.com/roar-jar/whytree-mcp.git ~/.claude/skills/whytree

One-line install or update

if [ -d ~/.claude/skills/whytree ]; then
  git -C ~/.claude/skills/whytree pull
else
  git clone https://github.com/roar-jar/whytree-mcp.git ~/.claude/skills/whytree
fi

Use

In Claude Code, run:

/whytree

What the skill does

Why Tree acts like a lightweight logic-tree / design-thinking layer before execution:

  1. clarify what the user is actually trying to do
  2. surface why it matters now
  3. expose missing constraints or success criteria
  4. turn that into a reusable prompt or brief

Example outcome

Input:

논문 쓸 거야

Output shape:

Task: 요청을 구체적인 research 브리프와 다음 실행으로 전환: 논문 쓸 거야
Purpose: "논문 쓸 거야"라는 요청 뒤의 실제 의도를 실행 전에 먼저 분명히 한다...
Why now: 연구를 시작하려면 주제·질문·자료 범위를 먼저 분명히 해야 한다.
Problem framing: 지금 막힌 지점이 연구질문 정의인지, 목차 설계인지, 선행연구 확보인지 나눠서 본다.
Success signals: 연구 질문이 한 문장으로 정리된다 ...

Advanced: MCP package

This repository also includes an MCP package named whytree-mcp for advanced users who want to run Why Tree as an MCP server.

Run with npx

npx -y whytree-mcp

Claude Code / Claude Desktop MCP config

{
  "mcpServers": {
    "whytree": {
      "command": "npx",
      "args": ["-y", "whytree-mcp"]
    }
  }
}

Local development

npm install
npm test
npm pack --dry-run

npm trusted publishing setup

For the MCP package release flow, configure npm trusted publishing for:

  • repository: roar-jar/whytree-mcp
  • workflow file: .github/workflows/publish.yml
  • environment: none required

License

MIT