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

@lostgradient/cinder-mcp

v0.0.0

Published

Model Context Protocol server exposing Cinder component discovery, comparison, and best-practice guidance to MCP clients.

Downloads

29

Readme

@lostgradient/cinder-mcp

A Model Context Protocol server exposing Cinder component discovery, comparison, and best-practice guidance to MCP clients — Claude Code, Codex, GitHub Copilot, and any other MCP-compatible agent.

It is read-only: every tool, resource, and prompt below reads Cinder's generated component manifest and metadata. Nothing it exposes writes to your project.

Install

npm install --save-dev @lostgradient/cinder-mcp

Installing this package pulls in @lostgradient/cinder, the @modelcontextprotocol/sdk, and zod as regular dependencies — nothing else to install, and installing @lostgradient/cinder on its own never pulls in the MCP SDK or zod.

Requirements

  • Node.js >= 18. The published cinder-mcp binary is Node-only — no Bun installation is required to run it.

Launch

Every client below should invoke the installed binary the same way:

npx --no-install cinder-mcp

--no-install resolves the binary already installed in your project's node_modules/.bin — it never reaches out to the npm registry at invocation time.

Client configuration

Verified against each client's current documentation as of this package's initial release. If a client changes its schema, prefer that client's own docs over this file.

Claude Code — .mcp.json

{
  "mcpServers": {
    "cinder": {
      "command": "npx",
      "args": ["--no-install", "cinder-mcp"]
    }
  }
}

Source: Claude Code MCP docs. A server entry with no url is read as stdio automatically — no "type" field is needed.

Codex — .codex/config.toml

[mcp_servers.cinder]
command = "npx"
args = ["--no-install", "cinder-mcp"]
default_tools_approval_mode = "auto"

Source: Codex configuration reference. default_tools_approval_mode is optional — omit it to use Codex's interactive default.

GitHub Copilot (repository / coding agent) — .github/workflows MCP configuration

The GitHub Copilot coding agent's repository-level MCP schema requires an explicit type and a tools allow-list:

{
  "mcpServers": {
    "cinder": {
      "type": "local",
      "command": "npx",
      "args": ["--no-install", "cinder-mcp"],
      "tools": ["*"]
    }
  }
}

Source: Configure MCP servers for Copilot coding agent. "tools": ["*"] allows every tool this server exposes; list individual tool names (search_components, get_component, compare_components, get_best_practices) to narrow the allow-list.

VS Code Copilot — .vscode/mcp.json

VS Code's schema uses servers, not mcpServers, and does not require a type field for a stdio server:

{
  "servers": {
    "cinder": {
      "command": "npx",
      "args": ["--no-install", "cinder-mcp"]
    }
  }
}

Source: Use MCP servers in VS Code.

What it exposes

Tools

  • search_components — search Cinder components by purpose, id, tag, category, guidance, or overlap family.
  • get_component — manifest guidance plus schema, variables, examples, and constraints for one component.
  • compare_components — compare two or more components using manifest useWhen/avoidWhen/overlap guidance.
  • get_best_practices — Cinder import, style, metadata, and overlap decision guidance.

Resources

  • cinder://manifest — the full generated Cinder component manifest.
  • cinder://component/{id} — manifest guidance and generated artifacts for one component.
  • cinder://component/{id}/schema, /variables, /examples, /constraints — the generated artifact for one component.

Prompts

  • choose_cinder_component — guide an agent to choose an appropriate Cinder component before writing UI.
  • review_cinder_usage — review code for Cinder import, style, metadata, and component-choice best practices.

Non-goals

This package deliberately does not add HTTP/SSE/authenticated transports, write-capable tools, or Chat/Editor discovery. See the package boundaries decision for the full rationale behind the @lostgradient/cinder / @lostgradient/cinder-mcp split.