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

mcp-lawted-components

v4.0.0

Published

MCP server for UI component library

Readme

Lawted Components MCP Server

An MCP server that provides access to Lawted UI component documentation for LLMs.

What is MCP?

The Model Context Protocol (MCP) is a standardized way for applications to provide context to LLMs.

Features

  • Provides component library documentation via MCP
  • Allows agents to list and query available UI components
  • Exposes detailed component properties, examples, and usage patterns

Components Directory

The server reads component definitions from JSON files in a specified components directory. You must provide the path to this directory when running the tool.

Usage

This tool is designed to be run using npx, which downloads and executes the package without needing a local installation.

Prerequisites

  • Node.js 18+
  • npm (for using npx)

Running the Server

You need to specify the path to your components directory using either the --components-dir (or -d) flag or the LAWTED_COMPONENTS_DIR environment variable.

Example Configuration (e.g., for Cursor):

Some tools might require you to specify the command and arguments separately. Here's an example of how you might configure it in a tool like Cursor:

"lawted-components": {
  "command": "npx",
  "args": [
    "-y",
    "mcp-lawted-components",
    "-d",
    "/path/to/your/components"
  ]
}

(Remember to replace /path/to/your/components with your actual path)

Available Resources (For MCP Clients)

  • lawted://components - List all available components
  • lawted://component/{name} - Get details about a specific component
  • lawted://search/{query} - Search for components

Available Tools (For MCP Clients)

  • list-components - List all available components (returns a JSON string summary)
  • get-component - Get detailed information about a specific component (returns a JSON string)

Component Schema

Component JSON files should follow the structure defined in JSON-CREATE.md. See that file for the detailed schema.

Previously, an example schema was shown here, but due to its complexity, please refer to JSON-CREATE.md for the canonical definition.

Development

If you want to contribute or run the server locally for development:

Installation

git clone <repository-url>
cd mcp-lawted-components
npm install

Build

npm run build

Run Locally

node dist/index.js -d /path/to/your/components