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

capy-mcp

v1.1.2

Published

MCP server that inspects a repo, returns a structured /preview brief, and writes a design-system JSON artifact for AI coding agents

Readme

capy-mcp

capy-mcp is a stdio MCP server that inspects a React or Next.js repo and returns a structured brief for building or updating a local /preview route.

It does not generate the preview page itself. It gives an AI coding agent the repo map, inspection order, constraints, warnings, and target preview file so the agent can implement /preview in the host app.

What it exposes

The server currently registers three MCP tools:

  • get_preview_brief
  • update_preview
  • get_design_system

The tool accepts:

  • task: "build_preview" or "update_preview"
  • changedFiles?: a list of changed files to bias incremental updates
  • userGoal?: the end-user request so the brief stays aligned with the task

The tool returns structured content with:

  • project_facts
  • inspection_plan
  • constraints
  • deliverable_spec
  • update_strategy
  • warnings
  • instructions

get_design_system writes a stable JSON artifact, by default at .capy/design-system.json, and returns a summary plus the artifact contents. This file is meant to be the machine-readable source of truth that later coding sessions can load before making UI changes.

update_preview writes .capy/preview-state.json, diffs the current repo against the prior snapshot, refreshes .capy/design-system.json, and returns an incremental /preview update brief. This works even if the repo is not using git.

Install

npm install capy-mcp

Run it directly:

npx capy-mcp

MCP config

Example stdio MCP config:

{
  "mcpServers": {
    "capy": {
      "command": "npx",
      "args": ["-y", "capy-mcp"]
    }
  }
}

Library usage

import {
  buildDesignSystemArtifact,
  buildPreviewBrief,
  buildPreviewStateSnapshot,
  detectFramework,
  runPreviewUpdate,
  writeDesignSystemArtifact,
  writePreviewStateSnapshot,
} from "capy-mcp";

const framework = await detectFramework(process.cwd());
const brief = await buildPreviewBrief(process.cwd(), {
  task: "build_preview",
});
const designSystem = await buildDesignSystemArtifact(process.cwd());
await writeDesignSystemArtifact(process.cwd());
const previewState = await buildPreviewStateSnapshot(process.cwd());
await writePreviewStateSnapshot(process.cwd(), ".capy/preview-state.json", previewState);
const update = await runPreviewUpdate(process.cwd());

Local development

npm install
npm test
npx capy-mcp

Publish checklist

npm test
npm publish

If capy-mcp is not owned by your npm account, rename the package before publishing.