Docker Composer throwing an error

[hriziya]

Dokploy: 0.28.8 (latest version)

Here is the output of Claude Cowork.

Hitting a snag — the Dokploy MCP is returning a 400 Bad Request every time I try to create the compose service, even with minimal parameters. This is likely a version mismatch: newer Dokploy versions (v1.x) require an environmentId when creating services, but the MCP tool only exposes projectId.

Your project has environment ID hc5HtaG3XXXXI (the default "dev" environment), but there's no way to pass that through the current MCP schema.

[vcode-sh]

This was a known bug in v1 classic mode -- compose.create exposed projectId instead of the required environmentId.

Fixed in v2.0.0+ (current latest: v2.2.0).

The classic endpoint-per-tool surface has been replaced by Code Mode (search + execute). The generated SDK uses the correct parameters from the Dokploy OpenAPI spec:

await dokploy.compose.create({
  name: "my-compose",
  environmentId: "hc5HtaG3XXXXI",
  composeType: "docker-compose"
})

To upgrade:

npx @vibetools/dokploy-mcp@latest setup

Closing as fixed. If you hit any issues on v2.2.0, please open a new issue.