Coolify MCP Server

create_private_key

Creates an SSH private key in Coolify for server authentication or Git repository access.

Instructions

Create a new SSH private key in Coolify for server authentication or Git repository access.

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>",
      "private_key": "<private_key>"
    },
    "name": "create_private_key"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	A unique, human-readable name for the private key
`description`	No	Optional description of the key's purpose or usage
`private_key`	Yes	The SSH private key content in PEM format. Must be a valid SSH private key.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the creation action without mentioning side effects (e.g., overwriting existing keys), authentication requirements, or any destructive potential. This is insufficient for a tool handling sensitive SSH keys.

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 a single, well-structured sentence that front-loads the core action and context. Every word is meaningful without unnecessary verbosity.

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?

For a tool that creates sensitive SSH keys, the description lacks important context such as idempotency (what happens if key name exists), permission requirements, storage behavior, or any validation steps. No output schema, so return value has no documentation. This leaves gaps for an agent to misuse.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all three parameters. The description adds little beyond the schema, providing only context about usage (server or Git). Baseline 3 is appropriate as the schema already clarifies parameter meaning.

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 specifies the verb 'Create', the resource 'SSH private key', and the context 'in Coolify for server authentication or Git repository access'. It distinguishes this tool from sibling tools which create other resources.

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 implies the tool should be used to generate SSH keys for server or Git access, but does not explicitly state when to use it versus alternatives, or conditions like required permissions. No guidance on when not to use.

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