Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-create

Create a new Dokploy server by providing its IP address, SSH key, username, port, and server type for deployment or build tasks.

Instructions

POST /server.create

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": {
      "name": "<name>",
      "description": "<description>",
      "ipAddress": "<ipAddress>",
      "port": "<port>",
      "username": "<username>",
      "sshKeyId": "<sshKeyId>",
      "serverType": "<serverType>"
    },
    "name": "server-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
portYes
sshKeyIdYes
usernameYes
ipAddressYes
serverTypeYes
descriptionYes
enableDockerCleanupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations declare only openWorldHint=true; nothing covers the mutation profile, permissions, or consequences. The description adds nothing about what is created, whether it is reversible, what happens on duplicate IP/host, or what the response contains — leaving a destructive-looking write with zero behavioral context.

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

Conciseness2/5

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

It is short, but this is under-specification rather than conciseness. The single token-like line is not front-loaded with any useful information beyond an HTTP method and route.

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

Completeness1/5

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

For a create operation with 7 required parameters, an enum-typed serverType, and no output schema, the definition is essentially empty. An agent has no basis to fill required fields correctly or to anticipate side effects.

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?

Schema description coverage is 0% across 8 parameters, 7 of them required, so the description carries the full burden and does not compensate at all. Nothing explains the semantics of ipAddress, sshKeyId, serverType (deploy vs build), or enableDockerCleanup's default behavior.

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

Purpose2/5

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

"POST /server.create" only restates the tool name as an HTTP verb + path. It conveys that something is created, but not what a "server" is in this system, what gets provisioned, or how it differs from siblings like server-setup or server-validate.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as server-setup or server-update. An agent cannot infer from the description whether this registers an existing host or provisions a new one.

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

Deploy Server

Other Tools