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

stackmcp

v1.2.9

Published

Orchestrate your MCP servers — run stacks, track history, discover patterns

Readme

stackmcp.io

Orchestrate your MCP servers — combine tools into reusable stacks, track execution history, and discover patterns.

curl -fsSL https://stackmcp.io/install.sh | sh
stackmcp init
stackmcp daemon start
stackmcp stacks

What it does

StackMCP runs a local daemon that connects to your MCP servers and gives you a unified CLI and API on top of them:

  • Execute tools — call any tool from any MCP server through one endpoint
  • Run stacks — chain tools into reusable workflows (fetch-to-obsidian, youtube-to-obsidian, etc.)
  • Track history — every tool call and stack execution is recorded
  • Discover patterns — the recommendations engine surfaces repeated sequences

Quickstart

# 1. Interactive setup — picks MCP servers to enable
stackmcp init

# 2. Start the daemon (auto-starts when you run any command)
stackmcp daemon start

# 3. List available stacks
stackmcp stacks

# 4. Run a stack
stackmcp run fetch-url --url "https://example.com"
stackmcp run fetch-to-obsidian --url "https://serpapi.com/blog/the-state-of-mcp"

Example stacks

| Stack | What it does | |---|---| | fetch-url | Fetch any URL and get the content | | fetch-to-obsidian | Fetch a URL and save to Obsidian | | youtube-transcript | Get transcript of any YouTube video | | youtube-to-obsidian | Transcribe video and save as note | | deepseek-chat | Chat with DeepSeek AI | | github-search-repos | Search GitHub repositories | | calendar-to-obsidian | Log today's events to Obsidian | | puppeteer-screenshot | Screenshot a webpage |

CLI

stackmcp stacks              List stacks
stackmcp run <id> --key val  Execute a stack
stackmcp history             Recent executions
stackmcp recommendations     Repeated pattern insights
stackmcp init                Interactive server setup
stackmcp daemon start|stop   Manage the daemon

How it works

   CLI ──HTTP──▶  Daemon (port 3001)
                    │
                    ├── Filesystem MCP
                    ├── Fetch MCP
                    ├── GitHub MCP
                    ├── Obsidian MCP
                    ├── YouTube MCP
                    └── ... (any MCP server)

The daemon starts all configured MCP servers, aggregates their tools, and exposes a REST API. Stacks define multi-step workflows where tool outputs flow to downstream tools automatically.

Requirements

  • Node.js 18+
  • An MCP server to connect (or use the built-in Fetch, Filesystem servers)

Development

npm install
npm run daemon           # Start the daemon
node bin/stackmcp stacks # Run CLI commands
bash test/cli-smoke.sh   # Smoke tests