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

@byscott-io/widgetsbyscott

v0.1.16

Published

Local stdio MCP that mirrors widgets.byscott.io — create, view, and share charts/markdown/html/grid/tabs/index widgets in-memory with a live browser dashboard. Successor to chartsbyscott.

Readme

@byscott-io/widgetsbyscott

A local stdio MCP server that lets an AI agent build charts, markdown, HTML, tables and nested layouts, and watch them appear in a live browser dashboard.

Widgets live in memory for the life of the process. Nothing is written to disk and nothing is sent anywhere — close the server and they are gone. It mirrors the tool names and argument shapes of the hosted MCP at widgets.byscott.io, so an agent can move between local and hosted without knowing which one it is talking to.

Successor to chartsbyscott.

Use it

No install required:

npx @byscott-io/widgetsbyscott

It speaks MCP over stdio, so normally you point a client at it rather than running it yourself. For Claude Code:

{
  "mcpServers": {
    "widgetsbyscott": {
      "command": "npx",
      "args": ["-y", "@byscott-io/widgetsbyscott"]
    }
  }
}

On the first tool call it opens http://localhost:3110 in your browser. The dashboard updates over a WebSocket as widgets are created and changed, so you can leave it open beside the conversation.

Tools

| Tool | Does | |---|---| | create_widget | Create one. Requires type and title. | | update_widget | Change a widget by id or slug; pass only the fields you want changed. | | list_widgets | Metadata only, no content. Optional type filter, limit (default 50, max 200). | | get_widget | One widget with full content, by id or slug. Use this to read data back for analysis. | | delete_widget | Remove one by id or slug. |

Widget types

Leaf types carry their own content:

  • chart — chart_type (line, bar, pie, doughnut, radar, polarArea, bubble, scatter) plus data and optional options, in Chart.js shape: { labels, datasets: [{ label, data }] }.
  • markdown — source.
  • html — html, sanitized unless you pass sanitized: false.
  • table — data, same shape as chart.

Container types take a children array of { widget_id, position?, label? } instead of content:

  • grid — children laid out together.
  • tabs — children as tabs, using each child's label.
  • index — a listing of children; optional display_mode of list, cards or table.

Every widget has a visibility of private, account (the default) or public, and a slug that forms its address.

Configuration

| Variable | Default | Effect | |---|---|---| | WBS_HTTP_PORT | 3110 | Port for the dashboard and its WebSocket. | | WBS_NO_OPEN | unset | Set it to stop the browser being opened on the first tool call. The dashboard still runs and its URL is logged to stderr. Set to 0, false or no to keep the default opening behaviour. |

WBS_NO_OPEN is what you want in CI, on a headless host, or in any test that calls a tool — without it, exercising a single tool hijacks whatever browser is to hand.

Logs go to stderr only. Stdout is reserved for the MCP protocol, so anything printed there would corrupt the stream.

License

MIT.