coolify-mcp

Start application

startApplication

Idempotent

Launch a Coolify application using its UUID, with options to force rebuild or use instant deployment when updates must go live quickly.

Instructions

Start an application by UUID. Optionally force rebuild.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuid": "<uuid>"
    },
    "name": "startApplication"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes
`force`	No
`instant_deploy`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate the safety profile (readOnlyHint false, idempotentHint true, destructiveHint false). The description adds the 'force rebuild' behavior, which is useful, but it does not explain what force rebuild entails or any side effects. Some value is added beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is exceptionally concise: two short sentences, front-loaded with purpose. Every word earns its place, with no unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three parameters and no output schema, yet the description only covers the core start action and force rebuild. It omits important context about what happens when starting, behavior if already running, and the role of instant_deploy. Given the complexity of the surrounding toolset, this is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides no descriptions, and the description explains 'uuid' and 'force' only implicitly. The 'instant_deploy' parameter is completely unexplained. With 0% schema description coverage, the description fails to sufficiently compensate for the undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb and resource: 'Start an application by UUID.' It is distinct from sibling tools like stopApplication, restartApplication, and deploy. The optional force rebuild adds useful specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The implied usage is to start an application, but there is no explicit guidance on when to use this versus alternatives like restartApplication or deploy. No exclusions or conditions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server