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

@luckystack/mcp

v0.2.5

Published

Read-only MCP server that exposes a LuckyStack project's committed AI context (decisions, dependency graph, routes, runbooks, capabilities) to Claude Code as queryable tools.

Downloads

425

Readme

@luckystack/mcp

Read-only MCP server that exposes a LuckyStack project's committed AI context to Claude Code as queryable tools — so an agent can ask precise questions instead of loading whole index files into context.

Install

Nothing to install in your app — it runs via npx. Add it to your project's .mcp.json:

{
  "mcpServers": {
    "luckystack": { "type": "stdio", "command": "npx", "args": ["@luckystack/mcp@latest"] }
  }
}

create-luckystack-app adds this automatically when AI instructions are enabled. Claude Code launches the server with your project root as the working directory.

Tools

| Tool | Answers | | --- | --- | | blast_radius(file) | "What breaks if I change this file?" (transitive importers) | | who_imports(file) | "What directly imports this?" | | god_nodes(limit?) | "Which files are risky hubs everything depends on?" | | list_decisions(tag?) | "What did we decide, and about what?" | | get_decision(id) | "Why did we decide X?" (full ADR) | | find_route(query) | "Which API/sync routes match this?" | | get_runbook(task?) | "How do I add an API/page/sync/helper here?" | | get_capability(name) | "Does a helper/component for this already exist?" |

All tools are read-only and read committed artifacts (docs/ai-graph.json, docs/decisions/, docs/AI_*.md). If an artifact is missing, the tool tells you which npm run ai:* command generates it.

It is independent of the playwright / chrome-devtools browser MCP servers — they coexist as separate entries in the same .mcp.json.

License

MIT