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

mc-puppet

v0.1.2

Published

See and drive a running Minecraft from a script, CI or an AI coding agent: the command line tools and MCP server for the MC Puppet mod.

Readme

mc-puppet

The command line tools and MCP server for MC Puppet, a Minecraft mod that lets a program on the same machine see and drive a running game — the open screen as data, clicks and keys through the game's own input handlers, commands with their output, screenshots — so a mod can be tested without a person at the keyboard.

These tools talk to the mod; they do nothing without it.

No dependencies; Node 18 or later. The tools and the mod say which version of the protocol they speak, and a mismatch is reported as one: mc-puppet version.

npx mc-puppet status                        # which games are listening
npx mc-puppet client screen                 # the open screen: widgets, slots, a merchant's offers
npx mc-puppet client click_widget text=Done
npx mc-puppet server command '{"command":"time set day"}'
npx mc-puppet run scenarios/trade.json --junit results.xml
npx mc-puppet launch client --loader fabric --world my_world   # a dev game through your Gradle wrapper
npx mc-puppet stop

--dir <gameDir> says where to look, or MC_PUPPET_DIRS; a mod project's root will do, since run, fabric/run, neoforge/run and forge/run under it are looked in.

For AI coding agents

"mc-puppet": {
  "type": "stdio",
  "command": "npx",
  "args": ["-y", "mc-puppet", "mcp"],
  "env": { "MC_PUPPET_DIRS": "/path/to/your_mod" }
}

Five tools: puppet_status, puppet_help, puppet_call, puppet_run and puppet_screenshot. The game describes its own operations, so the list stays short.

Outside a development environment

The mod is off unless switched on, listens on 127.0.0.1 only, and wants a token it makes afresh each start. In a real launcher's instance that is still not enough, because a modpack ships its config folder: the game directory has to be allowed from your home directory, one at a time.

npx mc-puppet allow "C:/games/my-instance"     # and: disallow, allowed

Nothing you download should ever write there. If a game you did not set up says MC Puppet is switched on and has stayed off, that is this at work, and nothing needs doing.

MIT.