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

@blackbelt-technology/pi-dashboard-mcp-client-plugin

v0.9.0

Published

First-party dashboard plugin managing pi's built-in MCP configuration: Pi-global + trusted-folder mcp.json view with live state from `pi mcp list`, validated atomic writes, and global + folder MCP management surfaces.

Readme

@blackbelt-technology/pi-dashboard-mcp-client-plugin

Dashboard plugin owning pi's MCP server configuration — the generic MCP server manager (create / edit / enable / disable, exposure / toolExposure, global + folder scope), live state from pi mcp list --json, and the effective config view. Uses pi's BUILT-IN MCP (pi ≥ 1.0.0); no pi-mcp-adapter.

Entries

| Export | Purpose | |---|---| | . / ./client | Settings claim + sidebar/worktree folder MCP section + /folder/:cwd/mcp page | | ./server | registerPlugin — provides mcp-client.config, mounts the REST surface | | ./core | Host-free logic (also consumed by the hostless apple-tools installer CLI) |

Two layers

Pi global $PI_CODING_AGENT_DIR/mcp.json (else ~/.pi/agent/mcp.json) and trusted <cwd>/.pi/mcp.json. A project entry replaces the global entry of the same name — whole entry, matching pi. Both layers parse as strict JSON.parse; a file with comments or trailing commas is skipped whole by pi and shown as unparseable. Trust comes from the injected isProjectTrusted(cwd) predicate (the server supplies host.isProjectTrusted).

mcp-client.config service

In-process service consumed by other plugins via ctx.consume("mcp-client.config") (declare dependsOn: ["mcp-client"]). Backed by merge-only Pi-owned writes: strict JSON parse, whole-entry replace, atomic 0o600 write, prototype-key refusal, and a closed refusal union (unparseable | entry-not-object | invalid-name | name-collision | transport-conflict | invalid-entry | write-failed).

| Method | Purpose | |---|---| | readServerEntry(name, scope) | Raw file entry from the scope's Pi-owned layer | | ensureServerEntry(name, fields, scope) | Merge a command/url transport + fields | | saveServer(name, entry, scope, previousName?) | Write a whole entry (optional rename) | | setEnabled(name, enabled, scope) | enabled: false, or remove the key | | removeServer(name, scope) | Delete one entry (returns the removed raw entry) | | convertAdapterLeftovers(name, scope) | Convert adapter disabled → enabled: false, drop other adapter keys | | previewEnsure(name, fields, scope) | Write-suppressed check parity with the writers | | readParseStatus(scope) | Per-layer strict-JSON parse status | | getLiveState(scope, { fresh? }) | pi mcp list --json rows (30 s timeout + cache) |

REST surface (networkGuard on every route)

| Route | Purpose | |---|---| | GET /api/mcp-client/effective?cwd= | Effective servers with provenance + live state (global secrets redacted) | | GET /api/mcp-client/live?cwd=&fresh=1 | Live state from pi mcp list --json | | GET /api/mcp-client/schema | Published config schema | | PUT /api/mcp-client/servers/:name | { scope, cwd?, entry, previousName? } | | DELETE /api/mcp-client/servers/:name?scope=&cwd= | Remove one server → { ok, removed } | | PUT /api/mcp-client/servers/:name/enabled | { scope, cwd?, enabled } | | POST /api/mcp-client/servers/:name/convert | { scope, cwd? } — convert adapter leftovers |

Project cwds must be in the known-folder set (host.knownFolderCwds) and trusted; otherwise the route answers 403 not-allowed with a reason/hint before any IO. Path names are decoded + validated first.

See change: extract-mcp-client-plugin, migrate-mcp-to-pi-builtin.