Everything an app on ml.ink needs — the repo, the service, the database, the domain — is reachable from one session, so shipping a change and finding out what the build did stop being two different places you have to go.
A hosted control plane for ml.ink, reached at https://mcp.ml.ink/mcp over Streamable HTTP. It covers the whole life of an app there — the git repo it builds from, the service that runs it, the database behind it, and the DNS in front of it.
- Deploy a service from a git repo, then change its repo, branch, port, env, resources or commands and redeploy on the latest code
- Build and runtime logs for a service, alongside the configuration it is running with
- A database provisioned — SQLite via Turso — with the connection URL and auth token read back when you need them
- A git repo created for you, internal or on GitHub, plus the token to push to it
- Custom domains attached to a service, and DNS records added, listed and removed
- Workspaces created, people invited, invitations accepted or declined, members listed and removed
- An action log of what has happened on the account
An ml.ink account. Clients that support OAuth sign in through the browser; otherwise generate an API key under Settings → API Keys and send it as an Authorization: Bearer header. Nothing to install — the server is hosted.
One command plus a key — claude mcp add --transport http ink https://mcp.ml.ink/mcp, then supply credentials