VitaminMCP

MCP clients can now share one VitaminMCP process over loopback HTTP, and on Windows one command installs it as a service.

Nothing breaks against 3.1.1. Stdio is still the default, the tools, their arguments and their answers are unchanged, and the server plugin is the same as in 3.1.1. One edge: the launcher used to ignore an argument it did not recognise, and now stops with a usage message.

Added

A shared HTTP mode. npx -y vitaminmcp --http serves MCP at http://127.0.0.1:25584/mcp — a port can follow the flag — for clients that would otherwise start one stdio server for every loaded project. Each client gets its own session, so its Minecraft connections and bots cannot be addressed by another client, and a bot runner still starts only after session_start. A session nobody has called for six hours is closed and its bots disconnect; a client that comes back after that starts a new session and calls session_start again. It works on every platform, under whatever service manager keeps the process running.

A Windows service for it. npx -y vitaminmcp service install installs the shared server as a service that starts with the machine, waits until the endpoint answers, and prints the client configuration to use. Windows asks for administrator approval once; no account password is asked for or stored. service status and service uninstall inspect and remove it, installing again updates it, and uninstalling keeps the Microsoft account and agent handshake data under ~/.vitaminmcp. The service lives in C:\ProgramData\VitaminMCP, which only administrators can read or change, and the install refuses if a folder of that name is already there.

Point each client at the URL instead of a command. For Codex:

[mcp_servers.vitaminmcp]
url = "http://127.0.0.1:25584/mcp"
startup_timeout_sec = 60

The shared endpoint has no token. It listens on loopback only, but every program and every account on the machine can use the agent handshakes and Microsoft accounts under ~/.vitaminmcp through it. Use it on a computer only you use, and stay on stdio on a shared one. Requests from web pages are refused, so a browser-based MCP client cannot connect to it.

Upgrading

Install as before; nothing changes unless you want the shared mode. To switch a client over, replace its npx -y vitaminmcp entry with the URL above and restart it once.

The shared mode and the service installer were contributed by @qsef1256.

Full Changelog: https://github.com/Backas03/VitaminMCP/compare/3.1.1...3.2.0