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

@kazee-ds/mcp

v0.1.18

Published

Versioned React and Vue documentation tools for Kazee Design System agents

Readme

Kazee Design System MCP

Prepared, unpublished version 0.1.18 retains npm-verified 0.10.3 and earlier catalogs from checksum-verified npm archives. Catalog 0.10.3 covers React 0.10.3, Vue 0.10.2, styles 0.11.0 and tokens 0.7.0; catalog 0.10.2 covers React 0.10.2, Vue 0.10.1, styles 0.10.3 and tokens 0.6.1. Use get_catalog_versions to check exact available catalogs. See the release record.

The workspace preview (React/Vue 0.12.0, styles 0.13.0) adds popoverAlign/popoverProps/popoverWidth for Select/Combobox/DateRangePicker/temporal picker popovers, fixes RTL popover alignment and a Vue uncontrolled-open bug, and fixes the Tabs pill/secondary indicator, enclosed actions/extras centering and chip ToggleButton hover/press contrast. It bundles tokens 0.8.0 unchanged. Published styles 0.11.0 / tokens 0.7.0 added the AA --ds-color-text-secondary text role, which remains unchanged. The 0.10.0 catalog includes Combobox sizing/focus/nonempty-selection and Dialog dividers. React and styles 0.10.1 add the repeated-focus/toggle and fixed-width fixes without changing the public API.

Read-only, offline stdio tools for the public React and Vue APIs. No Storybook process is required. The server never installs packages, executes commands, scans a project or reads registry credentials.

The workspace preview documents the current React/Vue 0.12.0 and styles 0.13.0 behavior above, plus the previously prepared enclosed Tabs variant and nested Tabs scoping (React/Vue 0.11.0, styles 0.12.0, tokens 0.8.0). New behavior stays out of the retained published catalogs. The configuration below remains pinned to the last verified published MCP 0.1.16.

Configuration

Merge this entry into the application's Claude Code .mcp.json:

{
  "mcpServers": {
    "kazee": {
      "command": "npx",
      "args": ["-y", "@kazee-ds/[email protected]"]
    }
  }
}

Before publication, use node with the absolute bin/kazee-mcp.mjs path from a local checkout or installed .tgz package. Other clients use their own MCP configuration format. Preserve existing servers; restart/reconnect the client after configuration changes. Public npm downloads need no read token; the running server itself needs no network connection. Keep actual tokens out of .mcp.json.

MCP 0.1.8 adds verified catalog 0.5.5 (React/Vue/styles 0.5.5, tokens 0.4.4, lint 0.4.2) with contrasting field/control boundaries and decorative subtle borders. Earlier catalogs retain their original token values.

Tools

MCP 0.1.8 retains registry-verified catalogs 0.2.0, 0.3.0, 0.4.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, and 0.5.5. The 0.5.4 catalog uses React/Vue/styles 0.5.4, tokens 0.4.3 and lint 0.4.2, with consistent subtle borders (#DBDBDB in light mode). The 0.5.3 catalog uses React/Vue/styles 0.5.3 and tokens/lint 0.4.2, with guarded Toast keyboard handling. The 0.5.2 catalog uses React/Vue/styles 0.5.2 and tokens/lint 0.4.1; the retained 0.5.1 catalog keeps its original tokens/lint 0.4.0. These snapshots come from actual npm archives with checksum provenance, including Toast/ToastProvider and optional close/progress controls.

Use the exact installed framework version. The retained 0.10.3, 0.10.2, 0.10.1, 0.10.0, 0.8.0 and 0.6.0 catalogs come from verified npm archives. The separate 0.12.0-workspace (React/Vue) / 0.13.0-workspace (styles) preview is for checkout review and matching local packed artifacts; it is not a verified registry catalog. Publish this MCP candidate, verify availability, then update the client pin and reconnect. Historical catalogs retain their original APIs.

Public npm installation needs no read token. Historical snapshots retain their original registry provenance and are never overwritten. See the version matrix.

  1. get_catalog_versions: exact supported versions and provenance.
  2. list_components: browse/search by framework, version, function or keyword.
  3. get_component_docs: public props, discriminated variants, related types, Vue events/slots and composition limits.
  4. get_component_examples: complete, typechecked TSX/Vue examples.
  5. get_theme_variables: semantic light/dark CSS variables and resolved values.
  6. get_installation: pinned package commands, global CSS and lint guidance.
  7. get_guides: agent workflow, framework differences, styling and application composition.

All tools carry read-only annotations. kazee://guides/workflow and kazee://catalog/versions are also exposed as resources.

Always supply the exact installed framework package version, obtained from its public package manifest or lockfile. The server rejects unknown versions instead of substituting newer APIs. Both 0.2.0 (eight components per framework) and 0.3.0 (32 per framework) use declarations and tokens extracted from published GitLab registry archives. Their provenance retains SHA-256 archive hashes. The retained catalogs correct the stale candidate label shipped in MCP 0.1.0. Publishing a new MCP catalog is a separate release step. Registry verification records a build-time check, not live registry availability.

Examples use public @kazee-ds/react / @kazee-ds/vue imports. The package does not provide shadcn-style component source installation or hosted HTTP transport. MCP supplies reference material; AGENTS.md and consumer lint guide and enforce usage. Successful tool calls do not establish agent instruction-following or production adoption.