For developers

Run your Minecraft server from code

Programmatic hosting — REST API, TypeScript SDK, CLI, and MCP. The same never-oversold CPU and live TPS you get in the panel, now scriptable.

Read the docs ↗Get an API key
The dev loop

Build your plugin and it's live

truetick dev watches the jar your build produces and, when it changes, uploads it over SFTP → restarts the server → tails the live log. Your dev server is metered and scale-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 ↗

$ truetick login --key ttk_…
$ truetick init --create --name Dev --ram 4096 --type PAPER --yes
$ truetick dev
new jar → upload → restart → live logs, on every build
Four ways in

One platform, four surfaces

REST API

Manage servers, files, backups, and mods over HTTP. Scoped ttk_ keys via the x-api-key header, rate-limited, no admin endpoints exposed.

curl -H "x-api-key: ttk_…" https://api.truetick.gg/v1/whoami

Docs ↗

TypeScript SDK

Typed client for servers, live metrics, console, files, backups, and mods.

npm i @truetick/sdk

Docs ↗

CLI

Manage servers from your terminal — plus a live dev loop for plugins and mods.

npx @truetick/cli servers list

Docs ↗

MCP server

Run and inspect your servers straight from Claude or any MCP client.

npx -y @truetick/mcp

Docs ↗

Enforced in code

The moat holds over the API

Read live TPS/MSPT from /metrics for tick-capable cores — the same never-oversold numbers as the panel. Keys are scoped, billing is metered or flat, same as the panel, and the public reference exposes zero admin endpoints. What you can't do in the panel, you can't do with a key.

Spin one up. Watch the tick for yourself.

Top up by card or PayPal. A sleeping metered server bills nothing.