SDKs, CLI & tooling

Preview Every client around the managed.dev API — the SDKs, the mf CLI, the Terraform provider, and the MCP server — is generated from a single OpenAPI 3.1 spec. The spec is the source of truth, and a CI release gate blocks any release where the spec and the running API have drifted.

Developer preview

The managed.dev public API is in active development. The SDKs, mf CLI, Terraform provider, and MCP server described here are part of the developer preview and may change before general availability.

One spec, no drift

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; the SDKs, CLI, Terraform provider, and reference docs regenerate from that one document; and the release gate fails the build if the generated artifacts no longer match what the API actually serves.

In practice that means three guarantees:

• The docs you’re reading match the code. The reference is generated from the same spec the SDKs are.
• Every SDK exposes the same surface. A capability available in Go is available in TypeScript and PHP, because all three come from one document.
• Upgrades are mechanical. A new endpoint shows up across every tool in the same release, typed and documented, rather than trickling in by hand.

A credibility claim, said plainly

Spec-as-source-of-truth with a zero-drift gate is the bar set by the best developer platforms, not by hosts. It’s worth being precise about one concrete gap: no managed-WP host ships an official Terraform provider — only community ones. Ours is generated from the same spec as everything else.

The tooling

SDKs — Go, TypeScript, PHP

Typed clients with built-in pagination, idempotency, retries, and job waiting. Go and TypeScript first, PHP alongside, Python to follow. See the SDK reference.

mf CLI

The official command-line client over the SDK — mf login, mf deploy, mf exec, mf logs --tail, plus saved exec bookmarks and batch. See the mf CLI guide and the CLI reference.

Terraform provider

forge_site, forge_environment, forge_team, and forge_api_key resources with runtime and scopes declared in HCL — codify your fleet and review changes before applying. See the Terraform guide.

MCP server

An official Model Context Protocol server over the SDK, so an AI agent can drive the API with the same scoped, idempotent, job-returning endpoints you do. See the MCP guide.

llms.txt

A machine-readable llms.txt index of the docs and reference, so coding assistants can ground answers in the current API surface rather than stale training data.

OpenAPI 3.1 spec

The source document itself — import it into your own codegen, an API client, or a contract test. Everything above is derived from it.

Where to start

If you’re scripting against your own account, reach for an SDK in your language, or the mf CLI for one-off commands and CI steps. If you’re managing infrastructure declaratively, use the Terraform provider. 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.

Caution

The SDKs, CLI, Terraform provider, and MCP server are part of the developer preview and ship across the API’s phased rollout. The code samples in the reference are illustrative until each tool reaches general availability — check each tool’s page for its current status.

Next steps

SDKsInstall and authenticate the Go, TypeScript, and PHP clients.

CLI referenceFull mf command reference, install, and configuration.

Terraform providerDeclare sites, environments, teams, and keys in HCL.

MCP serverDrive the API from an AI agent over a scoped, idempotent surface.