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

marble-headed-mcp

v0.1.44

Published

MCP server for Marble headed automation endpoints

Readme

marble-headed-mcp

Local-first MCP development setup (no npm publish needed to test).

Config files

  • mcp.local.json: runs local build (node dist/index.js)
  • mcp.prod.json: runs published npm package (npx [email protected])
  • mcp.json: active config used by your local Codex session

One-command switch for Codex + Claude

Use these commands from this repo:

  • npm run switch:mcp:dev
  • npm run switch:mcp:prod
  • npm run switch:mcp:status

What gets updated:

  • mcp.json in this repo
  • ~/.codex/config.toml ([mcp_servers.marble-headed])
  • ~/.claude.json (mcpServers.marble-headed globally + project entries)

After switching, restart active Codex and Claude sessions.

Common workflow

  1. Install deps once:
    • npm ci
  2. Switch to local MCP mode:
    • npm run use:mcp:local
  3. Build once (or use watch):
    • npm run build
    • or npm run watch
  4. Restart Codex session so MCP reloads from mcp.json.
  5. Test changes locally without publishing to npm.

Switch back to published MCP

  • npm run use:mcp:prod
  • Restart Codex session.

Publish flow (when ready)

  1. Keep testing locally until stable.
  2. Bump version:
    • npm version patch
  3. Publish:
    • npm publish --access public