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

zapier-discovery-mcp

v0.1.0

Published

MCP server for automation discovery — search Zapier's app directory and surface popular Zap templates between apps, with one-click create links. Bring your own Partner API client_id.

Readme

zapier-discovery-mcp

An MCP server for automation discovery. Zapier MCP executes automations — this server answers the question that comes first: what could I automate?

  • "What do people automate between Slack and Notion?" — real, popular Zap templates, each with a one-click create link
  • "Is there a Zapier integration for this tool?" — search the 9,000+ app directory
  • "Give me automation ideas for my CRM" — templates ranked by actual usage, not hallucinated

Sibling project: zapier-dev-mcp for building Zapier integrations.

Setup

You need a Zapier Partner API client_id — free with any Zapier integration, and not a secret (it ships in client-side embed code). See the Partner API docs for where to find yours.

Claude Code

claude mcp add zapier-discovery --env ZAPIER_CLIENT_ID=your_client_id -- npx -y zapier-discovery-mcp

Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "zapier-discovery": {
      "command": "npx",
      "args": ["-y", "zapier-discovery-mcp"],
      "env": { "ZAPIER_CLIENT_ID": "your_client_id" }
    }
  }
}

Optional: ZAPIER_API_BASE overrides the API host (testing, proxies).

Tools

| Tool | What it does | |------|--------------| | search_apps | Search the app directory by name; popularity-ordered without a query. Returns slugs for the next step. | | find_zap_templates | Popular ready-made Zap templates for one app or a pair — title, step chain (Slack → Notion), description, one-click create URL |

Design notes

  • Defensive parsing. Partner API responses are only partially documented; the client whitelists fields and handles both bare-array and enveloped responses rather than assuming shapes.
  • Testable without credentials. The smoke test runs a local HTTP mock of the Partner API and points the server at it via ZAPIER_API_BASE — full end-to-end over stdio with zero secrets. Missing ZAPIER_CLIENT_ID produces setup instructions as a tool error, not a crash.
  • HTML in titles/descriptions is stripped and truncated before it reaches the model.

Not affiliated with or endorsed by Zapier.

Development

npm install
npm test                 # offline unit tests (mocked fetch)
npm run build            # tsc → dist/
node scripts/smoke.mjs   # end-to-end against a local Partner API mock

License

MIT