# 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.2.0/wodby.zip) or [read the versioned skill index](/agent-skills/0.2.0/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-deploy](/agent-skills/0.2.0/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-get-started](/agent-skills/0.2.0/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.2.0/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.2.0/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-service](/agent-skills/0.2.0/wodby2-service/SKILL.md): Author Wodby 2 service manifests using existing services, inheritance, charts, and images; choose configuration mechanisms and validate the runtime contract without publishing it.
- [wodby2-stack](/agent-skills/0.2.0/wodby2-stack/SKILL.md): Author Wodby 2 stack manifests by composing existing services, links, derivatives, options, integrations, and storage; validate the composition without importing or deploying it.
- [wodby2-troubleshoot](/agent-skills/0.2.0/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, and metrics.

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.