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

mcpfold

v1.4.1

Published

One source of truth for your MCP servers — fold one config out to every client.

Readme


The context-window tax

Every MCP server you connect dumps its full tool schema into your agent's context window on every turn — used or not. mcpfold's local proxy curates the toolset per client, so each agent sees only the tools it needs. In a reproducible benchmark, curating a typical multi-server setup cuts tool-schema tokens by ~80%.

You write one canonical config, and mcpfold folds it out to every client (Claude Desktop, Cursor, VS Code, Windsurf, and more) — resolving secret references at sync time instead of hardcoding keys into a dozen client files.

Install

# npm (cross-platform)
npm install -g mcpfold

# or run without installing
npx mcpfold@latest init

# macOS / Linux — Homebrew
brew install dj-pearson/tap/mcpfold

# Windows — WinGet
winget install PearsonMedia.mcpfold
# or Scoop
scoop bucket add mcpfold https://github.com/dj-pearson/scoop-bucket && scoop install mcpfold

# Docker
docker run --rm -v "$PWD:/work" ghcr.io/dj-pearson/mcpfold --help

# curl (standalone binary, no Node required)
curl -fsSL https://raw.githubusercontent.com/dj-pearson/MCPFold/main/scripts/install.sh | sh

Quickstart

mcpfold init          # scaffold a canonical mcpfold config
mcpfold import        # pull in servers already configured in your clients
mcpfold sync          # fold the config out to every detected client
mcpfold diff          # preview what a sync would change, per client
mcpfold doctor        # diagnose config, clients, and secret references

mcpf is a shorter alias for mcpfold.

Why mcpfold

  • Cut the token tax — per-client tool curation trims schemas an agent never uses (~80% in the benchmark).
  • One source of truth — edit config once; every client stays in sync.
  • Secret references, not values — keep keys out of client config files; resolve them at sync time.
  • Local-first & private — the CLI and proxy run entirely on your machine.
  • Free forever, MIT-licensed — the optional hosted cloud (accounts, config sync, teams) is self-hostable.

Docs

Full documentation lives in the repo: https://github.com/dj-pearson/MCPFold · site: https://mcpfold.com

License

MIT © Pearson Media