# Wodby 2 for agents

Use these workflows to assess application fit, plan a migration, deploy and troubleshoot apps, or author reusable components.

MCP endpoint: `https://mcp.wodby.com/mcp`. Authenticate through your client's OAuth flow. Guidance is public; account operations require authentication and the user's authorization.

[Download the Wodby plugin](/agent-skills/0.13.14/wodby.zip) or [read the versioned skill index](/agent-skills/0.13.14/index.json).

Extract the plugin and use your host's supported local-plugin installation or loading mechanism. The archive contains portable SKILL.md directories and a Codex-compatible plugin manifest with HTTP MCP configuration. Other hosts may require their own MCP setup. Installing files does not authorize or authenticate an account.

Start with `wodby2-get-started`, or `wodby2-migrate` for an application running elsewhere. Migration starts with a read-only plan; staging deployment and production cutover require separate authorization. Repository access comes from your agent, not Wodby MCP. Connected agents can call `get_wodby_guidance` with the relevant skill name; a local skill installation is optional.

- [wodby2-ci](/agent-skills/0.13.14/wodby2-ci/SKILL.md): Create or repair the Wodby CI pipeline and post-deployment scripts of a repository that builds a Wodby 2 app service, validate both files, and follow the first build. Covers moving the same steps to GitHub Actions, GitLab CI or CircleCI.
- [wodby2-cluster](/agent-skills/0.13.14/wodby2-cluster/SKILL.md): Choose, compare costs, create, size, scale and upgrade a Wodby 2 cluster. Use for hosting and budget questions too, including during migration planning. Covers managed Kubernetes, self-hosted K3s, Wodby Cloud and demo clusters, capacity and upgrades.
- [wodby2-connect](/agent-skills/0.13.14/wodby2-connect/SKILL.md): Connect an application's code to the services Wodby 2 runs for it, such as a database, cache, search, mail or file storage. Covers finding out what Wodby already generates and wires for the services of an environment, using it instead of adding settings to the code, and adding a service that is missing. Applies to deployed environments and development workspaces.
- [wodby2-create-app](/agent-skills/0.13.14/wodby2-create-app/SKILL.md): Create a new application from what the user wants to build, recommending the stack, boilerplate, repository and cluster, then hand the coding to Wodby Agent in a development workspace and take the result to production.
- [wodby2-data](/agent-skills/0.13.14/wodby2-data/SKILL.md): Protect and move the data of Wodby 2 applications and databases. Covers backup destinations and schedules, taking and verifying backups, restoring a backup, importing a dump or files, copying data from one environment to another, and standalone databases with their DBs and users.
- [wodby2-deploy](/agent-skills/0.13.14/wodby2-deploy/SKILL.md): Deploy an application to Wodby 2 using an existing stack or app environment, resolve prerequisites, follow builds and deployments, and verify the resulting runtime state.
- [wodby2-environment](/agent-skills/0.13.14/wodby2-environment/SKILL.md): Configure and operate an existing Wodby 2 app environment, covering environment variables, CPU, memory and replicas, cron schedules, domains, certificates and HTTP settings, protecting an environment with basic auth or Private App Access, moving it to another cluster, pausing, resuming and maintenance mode, a service's version, code branch, settings, config files, links, integrations and volumes, and upgrading to a newer stack revision. Apply a change with a deployment and verify it.
- [wodby2-get-started](/agent-skills/0.13.14/wodby2-get-started/SKILL.md): Assess application fit and prerequisites for Wodby 2, connect an agent, and choose an existing stack or the appropriate migration, deployment, troubleshooting, or authoring workflow.
- [wodby2-migrate](/agent-skills/0.13.14/wodby2-migrate/SKILL.md): Assess an existing application's migration to Wodby 2, map its runtime and data requirements, prepare a staged migration plan, and carry out only explicitly authorized deployment or cutover steps. Use for an app already running elsewhere, not an ordinary redeployment of a Wodby app.
- [wodby2-provider](/agent-skills/0.13.14/wodby2-provider/SKILL.md): Choose an existing Wodby 2 integration contract or author and validate a custom variable provider for reusable runtime configuration. Does not implement new OAuth or infrastructure providers.
- [wodby2-review](/agent-skills/0.13.14/wodby2-review/SKILL.md): Review a Wodby 2 app environment, an app or a whole organization without changing anything, and report what is unhealthy, unprotected or out of date, with what to fix first. Covers failed tasks, service health, backups, domains and certificates, resources, replicas and pending upgrades.
- [wodby2-service](/agent-skills/0.13.14/wodby2-service/SKILL.md): Author Wodby 2 service manifests using existing services, inheritance, charts, and images; choose configuration mechanisms, declare development workspace support, move an inherited service to a newer base version, and validate the runtime contract without publishing it.
- [wodby2-stack](/agent-skills/0.13.14/wodby2-stack/SKILL.md): Author Wodby 2 stack manifests by composing existing services, links, derivatives, options, integrations, and storage, and validate the composition without importing or deploying it. Also bring an organization's existing stack up to date, from its origin, its Git source or newer service revisions, add or remove a service such as Redis, and publish or discard its draft.
- [wodby2-troubleshoot](/agent-skills/0.13.14/wodby2-troubleshoot/SKILL.md): Diagnose failed or stuck Wodby 2 builds, deployments, and tasks or unhealthy app services using task logs, bounded live application logs, deployment state, pod status, metrics, and explicitly authorized container commands.

See the [Wodby 2 documentation](https://wodby.com/docs/2.0/) and [MCP setup](https://wodby.com/docs/2.0/dev/mcp/). These workflows do not apply to Wodby 1. Provider authoring currently ends at validation; integration setup may require a dashboard handoff.
