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

@caffinate/mcp-server

v0.1.2

Published

Caffinate MCP server — build, publish, install AI workflows from inside your agent runtime.

Readme

@caffinate/mcp-server

MCP server for Caffinate — build, publish, install, fork, and run AI workflows directly from inside your agent runtime.

Setup

1. Create an API key

Sign in at caffinate.vercel.app, go to Settings → API Keys, and mint a new key. You'll see the full caff_… value once; copy it.

2. Add the server to your agent runtime config

Most MCP-compatible runtimes read a JSON config like this:

{
  "mcpServers": {
    "caffinate": {
      "command": "npx",
      "args": ["-y", "@caffinate/mcp-server"],
      "env": {
        "CAFFINATE_API_KEY": "caff_your_key_here"
      }
    }
  }
}

Restart the runtime. The tools below become available in-session.

Tool surface

For consumers

| Tool | Purpose | |---|---| | caffinate_auth_status | Verify the API key is live; see which user you're authed as | | caffinate_search | Full-text search of the marketplace feed | | caffinate_workflow_info | Full metadata for a workflow by slug | | caffinate_install | Install a workflow into the current project | | caffinate_list_installed | Show what's installed in this project | | caffinate_list_starter_kits | List workflows in the Starter Kit category — one-install deployable scaffolds | | caffinate_run | Execute an installed workflow + record the run server-side | | caffinate_fork | Fork a workflow as your own editable copy (lineage recorded) |

For creators

| Tool | Purpose | |---|---| | caffinate_workflow_init | Scaffold a new workflow package in the current project | | caffinate_pack_preview | Validate a workflow directory without uploading | | caffinate_publish | Pack + upload + publish the workflow end-to-end |

How a workflow package works

A workflow is a directory with a caffinate.json manifest and one or more Markdown prompt files. Full manifest schema in @caffinate/workflow-format.

Creator economics

Split, enforced in backend code:

| Recipient | Share | |---|---| | Creator (direct) | 80% | | Platform | 18% | | Community burn | 2% |

Fork royalty to ancestors, per install of a descendant: 12% / 5% / 2% / 1% at depths 1–4.

License

MIT. Source in packages/mcp-server.