coolify-mcp

List servers

listServers

Read-only

Get a complete inventory of all Coolify servers, including UUID, name, IP, user, port, and proxy type, to manage your infrastructure.

Instructions

List all Coolify servers. Returns server UUID, name, IP, user, port, and proxy type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listServers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 2, 2026

TDQS

C2.9/5.0

Behavior1/5

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

The description claims 'List all Coolify servers', but the annotation openWorldHint=true indicates that the result may not be exhaustive. This is a direct contradiction. Beyond that, the description does not disclose pagination behavior or that the summary parameter may alter the response shape.

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 two concise sentences with no filler. It front-loads the verb and resource, then lists the return fields. Every sentence serves a purpose.

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 is simple, but the description is incomplete given the openWorldHint annotation and the undocumented parameters. The 'all' claim conflicts with the annotation, and the lack of parameter semantics means the agent cannot fully understand pagination or summary behavior. The return-field list is helpful but does not compensate for these gaps.

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

Parameters1/5

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

The schema defines three parameters (limit, offset, summary) with 0% description coverage. The tool description does not explain any of these parameters, leaving the agent without guidance on pagination or summary response formatting. Since coverage is low, the description must compensate but does not.

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 states a specific action ('List') and a specific resource ('all Coolify servers'), and identifies the return fields (UUID, name, IP, user, port, proxy type). This clearly distinguishes it from siblings like getServer (single server) and listResources (broader resource list).

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 description clearly implies the tool is for listing servers, but it does not explicitly state when to use this tool versus alternatives like getServer or listResources, nor does it mention how pagination (limit/offset) or the summary flag should be used. No exclusions or alternative guidance is provided.

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

Deploy Server