GitHub Actions
wodby/actions/setup-wodby-cli@v1Install and authenticate Wodby CLI with the official setup action, then run build, release, and deployment commands from a GitHub Actions workflow.
Developer resources
Automate Wodby from APIs, SDKs, CLI, and MCP clients
Build scripts, integrations, CI workflows, internal tools, and AI-assisted operations on top of Wodby's public automation surfaces.
Use the REST API directly, start from generated SDKs, run Wodby CLI for pipeline and terminal workflows, or connect an MCP client when you want model-assisted platform operations.
Pick the automation surface that matches the job
Wodby exposes several developer-facing interfaces so teams do not have to force every workflow through the same tool.
REST API
Automate Wodby resources directly through the public /v1 API when you need custom scripts, internal tools, or direct integrations.
Read API docsOfficial SDKs
Use generated SDK packages for PHP, Python, JavaScript and TypeScript, or Go when you want typed models and request helpers.
Read SDK docsWodby CLI
Run stack-aware build, release, deploy, task, and resource operations from CI systems, local terminals, or automation scripts.
Read CLI docsWodby MCP
Connect AI assistants and automation clients to Wodby through the MCP server with OAuth or API-key authentication.
Read MCP docsAutomate the platform objects teams work with every day
The public API is designed around Wodby's operational model, from organizations and projects down to app services, deployments, routes, tasks, backups, imports, and environment variables.
That makes it useful for internal portals, onboarding automation, CI helpers, reporting, compliance exports, and repeatable maintenance workflows.
API areas
organizationsprojectsappsapp instancesapp servicesbuildsdeploymentsclustersdatabasesintegrationsprovidersstacksbackupsimportstasksroutesenvironment variables
Start with working projects and delivery examples
Use a ready-to-customize application as your starting point, then adapt a tested pipeline pattern when you need more control over how it builds and deploys.
Wodby boilerplatesStart from ready-to-use projects for popular frameworks. Wodby can import a selected boilerplate into a new GitHub or GitLab repository.Browse boilerplatesWodby CI examplesAdapt copyable Wodby CI, GitHub Actions, GitLab CI, and CircleCI pipelines for common build patterns and application stacks.Browse CI/CD examples
Set up Wodby CLI in your CI provider
Start with the supported setup tool for your provider, then adapt a complete pipeline from the Wodby CI examples.
CircleCI
wodby/setup-wodby-cli@1Use the official CircleCI orb with a machine executor to install and initialize Wodby CLI before running the Wodby build and deployment flow.
GitLab CI
wodby/wodby-cli:2.0Run the official Wodby CLI container image in GitLab CI. Pipelines that build application images can pair it with Docker-in-Docker.
Use API keys for scripts, CI jobs, and SDK clients
API keys are created from user settings in the Wodby dashboard. Requests authenticate with X-API-KEY, while CI jobs and SDK examples typically pass the same value through WODBY_API_KEY.
Keys belong to an organization and run with the permissions of the user who created them, so automation can fit the same access model teams already use in the dashboard.
Start from generated SDK packages when application code is the right integration point
The official SDK packages target the Wodby 2 public API and are generated from the OpenAPI schema, so models and request helpers track the public REST contract.
| Language | Package | Install |
|---|---|---|
| PHP | wodby/wodby-sdk-php | composer require wodby/wodby-sdk-php |
| Python | wodby | pip install wodby |
| JavaScript and TypeScript | @wodby/sdk | npm install @wodby/sdk |
| Go | github.com/wodby/wodby-sdk-go/v4/pkg | go get github.com/wodby/wodby-sdk-go/v4/pkg |
Next step
Build on the public interface that keeps your workflow simple
Use API calls for custom integrations, SDKs for application code, CLI commands for pipeline and terminal automation, and MCP when an assistant needs controlled access to Wodby operations.