VitaminMCP

Installing this stopped being a four-step manual procedure. It used to begin with "download three jars and put each somewhere different". It is now two halves: one line for the client, and a command that does the server side for you.

Nothing breaks against 1.4.2.

Added

An npx launcher.

claude mcp add vitaminmcp -- npx -y vitaminmcp

It verifies what it downloads, so a corrupted or tampered file is refused rather than run. The bot runner is large and arrives in the background — the server answers immediately, and the first call that actually needs a bot waits for it.

/mcp__vitaminmcp__setup installs the plugin half. The part that happens on the Minecraft server used to be a README section you followed by hand. It is now a prompt that walks it: check the server version, place the jar, restart, read the console, connect. It asks before downloading anything and before changing server.properties, and says what each bot setting does before offering to set it.

session_start takes no arguments for a server on this machine. The agent generates its own token on first start, so there is nothing to copy out of a log. The response reports resolvedFrom, so a session that reached something unexpected says so rather than looking like a working one.

A server on another machine still needs host and token together. With several agents running, an omitted mcpPort is an error listing them rather than a pick.

Listed in the MCP registry, so it can be found rather than only linked to.

Fixed

runnerJar can now actually be omitted. It was documented as optional and worked only if you passed an explicit path.

Full Changelog: https://github.com/Backas03/VitaminMCP/compare/1.4.2...1.5.0