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

showcase-mcp

v0.2.3

Published

MCP server: publish a self-contained static site (HTML page, report, slide deck, demo, small game) and get back a stable, shareable link that's fast worldwide and inside mainland China.

Readme

showcase-mcp

Publish a self-contained static site from your agent and get back a stable, shareable link that's fast worldwide and inside mainland China — no deploy, no repo, callable from any project.

showcase-mcp is a tiny stdio MCP server. Drop it into your MCP client config with one secret (your publish token) and your agent gains two tools: showcase_publish and showcase_list.

Zero-config setup

Get a publish token from your dashboard at https://showcasemcp.com, then add this to your MCP client config (e.g. ~/.cursor/mcp.json):

{
  "mcpServers": {
    "showcase": {
      "command": "npx",
      "args": ["-y", "showcase-mcp"],
      "env": { "SHOWCASE_TOKEN": "sct_your_token_here" }
    }
  }
}

That's it — npx fetches and runs the latest version (no install, no absolute paths, works on any machine). The control plane defaults to production; the only thing you supply is your token.

Tools

  • showcase_publish — publish (or republish) a site, returns the URL. Provide either html (a single self-contained page) or files (a multi-file bundle with a root index.html). Re-publishing with the same sourceKey replaces the content in place — the link never changes.
  • showcase_list — list your live sites (URL, source_key, views, last update), so the agent can recover a sourceKey and republish instead of creating a duplicate.

Vendor every dependency. Visitors may be in mainland China, where external CDNs (unpkg / jsdelivr / cdnjs / Google Fonts / …) fail. Inline or bundle all libraries, fonts, CSS, and images and reference them by relative path.

Config (env)

| var | required | meaning | |---|---|---| | SHOWCASE_TOKEN | yes | your per-user publish token (sct_…), from the dashboard | | SHOWCASE_API_URL | no | control-plane base URL; defaults to the production host. Set it only to target a different deployment, e.g. http://127.0.0.1:8787 for local testing against wrangler dev |

Local development (this repo)

pnpm --filter showcase-mcp build      # esbuild → self-contained dist/index.js
pnpm --filter showcase-mcp smoke      # drives the built binary as a real MCP
                                      # server against a local control plane

The smoke expects the local control plane up on http://127.0.0.1:8787 (see the repo root README.md → "Run the local smoke") and uses the seeded P0a token by default.