Go SDK
A typed client with built-in pagination,
idempotency, retries,
job waiting, webhook verification, and a test
server. go get terriblegit.com/terrible/forge-go — see the
SDK reference.
Every client around the managed.dev API is driven by a single OpenAPI spec.
The Go SDK, the mf CLI, and the
MCP server are shipped and generated from it today; the
Terraform provider and further SDKs follow the same
pipeline. The spec is the source of truth, and CI gates block any release where
a generated client and the spec have drifted.
The whole point of spec-as-source-of-truth is that you never depend on a hand-written client that has quietly fallen behind the API. When an endpoint, field, or scope changes, it changes in the spec first — and the pipeline keeps the tools honest with three concrete gates in the Go SDK’s CI:
Because the mf CLI and the MCP server
are built on that SDK, the same guarantees flow through to them: a command or
tool maps to a real operation, typed the way the API actually serves it.
Go SDK
A typed client with built-in pagination,
idempotency, retries,
job waiting, webhook verification, and a test
server. go get terriblegit.com/terrible/forge-go — see the
SDK reference.
mf CLI
The official command-line client, built on the Go SDK — mf login,
mf deploy build --follow, mf envs exec, mf listen, and a --json
scripting contract. See the mf CLI guide and the
CLI reference.
MCP server
mf mcp — an official Model Context Protocol server, so an AI agent can
drive the API through 36 scoped, idempotent, job-returning tools. See the
MCP guide.
Terraform provider
Preview forge_site,
forge_environment, forge_team, and forge_api_key resources declared
in HCL — codify your fleet and review changes before applying. Designed,
not yet shipped. See the Terraform guide.
TypeScript & PHP SDKs
Preview Typed clients off the same generation pipeline as Go, with Python to follow. Not yet shipped — until then, the API is a plain JSON-over-HTTPS surface. See the SDK roadmap.
llms.txt
Preview A machine-readable llms.txt
index of the docs and reference, so coding assistants can ground answers
in the current API surface. Planned, not yet published.
If you’re scripting against your own account, reach for the
Go SDK, or the mf CLI for one-off commands
and CI steps — --json output and stable exit codes make it a good pipeline
citizen in any language. If you’re building an agent or an integration, the
MCP server gives you the same surface with the guardrails —
scoped keys, idempotency, async jobs — already in place.