Jigsaw
grok-budget-mcp is one piece of a growing family of projects, big and small. Here is how the pieces fit together, as seen from this one.
grok-budget-mcp you are here
A small local MCP server that tells a Grok Build agent how much of its weekly usage pool is left, the same figure as /usage. Read-only, unofficial endpoint.
Fregoli kin
A web application an agent can rewrite while it is running: capabilities are Cordis plugins mounted and unmounted in a live Node process.
A fellow piece of the same puzzle; no direct connection yet.
Hermetarium possible habitat
The world an agent wakes up in: an OCI image it may use freely as root, behind a wall with Squid as the only, logged way out.
A house this gauge could serve in two ways; neither is built or tested yet. Inside a habitat: a Grok Build inhabitant could load the server and ask about its own budget. The image would hold only a placeholder auth.json, and Squid would add the real grok login token from the host-side ACL, the way Hermetarium already injects vendor keys; the billing route would need its own ACL entry, and the token is short-lived, so it needs renewing. Next to the supervisor: a watching agent on the host could call get_budget, send a habitat to sleep while the weekly pool is empty and wake it after period_end. Hermetarium has no such sleep and wake yet, only create and destroy, and keeping a changed world is still open (hermetarium#9).