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

integrations

v0.0.1-beta.3

Published

CLI for integrations.sh — search the registry of agent integrations and read a domain's surface.

Downloads

488

Readme

integrations

CLI for integrations.sh.

npx integrations search stripe

Install globally with npm i -g integrations; the command is integrations.

Quickstart

integrations search stripe
integrations stripe.com
integrations detect resend.com
integrations help surface

search accepts a service name. A bare domain such as stripe.com is treated as a surface lookup.

Agent Output

For API-backed commands, stdout is human-readable only when attached to a TTY. When stdout is piped or --json is passed, stdout is exactly one JSON document. Diagnostics go to stderr. Errors in JSON mode print this shape to stdout and exit non-zero:

{"error":"unknown flag --example"}

Examples:

integrations search stripe | jq .
integrations stripe.com --json

integrations skill is the exception: it prints markdown by default so it can be redirected into an agent skill file. Use integrations skill --json for the structured form.

Skill

Print the bundled integrations.sh agent skill:

integrations skill
integrations skill --json

Install it for Claude-style skill loaders:

mkdir -p ~/.claude/skills/integrations-sh
integrations skill > ~/.claude/skills/integrations-sh/SKILL.md

MCP

Print connection details for the hosted public MCP server:

integrations mcp
integrations mcp --json

Claude Code:

claude mcp add --transport http integrations https://integrations.sh/mcp

The JSON form is:

{"url":"https://integrations.sh/mcp","transport":"streamable-http","tools":["detect","discover"]}

Commands

The API command surface is derived from https://integrations.sh/openapi.json at runtime. Operation IDs become kebab-case commands, path parameters become positional arguments, query parameters become flags, and enum/boolean parameters are validated locally.

integrations help
integrations help search
integrations help discover

Current public operations include search, detect, discover, and surface. As the OpenAPI spec adds operations, the CLI picks them up without a release.

discover can take up to a minute and is rate-limited by the hosted API to 3 requests per 60 seconds per IP.

Base URL and Cache

Set INTEGRATIONS_BASE to target another compatible host:

INTEGRATIONS_BASE=http://localhost:4321 integrations help

The OpenAPI spec is cached in the system temp directory using the server TTL and ETag. Use --no-cache to bypass the cache for one invocation:

integrations search stripe --no-cache

Build

bun run typecheck
bun run build
bun test