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

@arloui/mcp

v0.1.1

Published

Read-only Model Context Protocol server that exposes Arlo UI components, tokens, and docs to coding agents.

Readme

@arloui/mcp

A read-only Model Context Protocol server that gives coding agents live access to Arlo UI components, design tokens, and docs.

The server holds no content of its own — every tool call resolves to a fetch of a canonical Arlo UI URL, so an agent always sees exactly what is published on the site. It runs locally over stdio; your agent launches it as a subprocess.

Connect

Claude Code

claude mcp add arloui -- npx -y @arloui/mcp

Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json), or any MCP client:

{
  "mcpServers": {
    "arloui": {
      "command": "npx",
      "args": ["-y", "@arloui/mcp"]
    }
  }
}

Tools

| Tool | What it returns | | --- | --- | | arlo_search | Ranked components + foundations for a natural-language query | | arlo_get_component | Full spec for one component: variants, deps, tokens, and RN source | | arlo_get_token | A colour token (light + dark) or a scale token such as spacing.6 | | arlo_get_archetype | One of the nine screen archetypes: hierarchy, composition, gotchas | | arlo_get_foundation | A foundation topic as markdown (spacing, type, motion, color, …) | | arlo_list_docs | Every docs page that has markdown, grouped by section |

Configuration

| Env var | Default | Purpose | | --- | --- | --- | | ARLO_BASE_URL | https://arloui.com | Site the tools fetch from | | ARLO_REGISTRY_URL | <base>/r | Registry index + component entries |

Point these at a local site to develop against unreleased components.

License

MIT