Run your Minecraft server from code
A REST API, a TypeScript SDK, a CLI, and an MCP server. You get the same never-oversold CPU and live TPS as in the panel, and you can script it.
Build your plugin and it's live
truetick dev watches the jar your build produces. When the jar changes, it uploads the new jar over SFTP, restarts the server and tails the live log. Your dev server is metered and scales to zero. You pay while it's awake, and by default it goes back to sleep 8 minutes after the last player leaves (set idleTimeoutMinutes per server to change that).
Full walkthrough: deploy a plugin ↗
One platform, four surfaces
REST API
Manage servers, files, backups, and mods over HTTP. Requests authenticate with a scoped ttk_ key in the x-api-key header and are rate-limited. No admin endpoints are exposed.
TypeScript SDK
Typed client for servers, live metrics, console, files, backups, and mods.
CLI
Manage servers from your terminal, with a live dev loop for plugins and mods.
MCP server
Run and inspect your servers straight from Claude or any MCP client.
Same rules as the panel
Read live TPS/MSPT from /metrics for tick-capable cores. These are the same numbers the panel shows, from the same never-oversold CPU. Keys are scoped, billing is metered or flat as in the panel, and the public reference exposes no admin endpoints. A key can't do anything you can't do in the panel.
Start a server and watch its tick yourself
Top up by card or PayPal. A sleeping metered server bills nothing.