Kastell MCP Server

What the code does

We read the source, 15 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const proc = spawn(command, [], {

        const match = line.match(/^(\d{3,4})\s+(.*(?:id_rsa|id_ed25519|id_ecdsa|id_dsa|.*\.pem).*)/);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add kastell -- npx -y kastell

{
  "mcpServers": {
    "kastell": {
      "args": [
        "-y",
        "kastell"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.kastell]
command = "npx"
args = ["-y", "kastell"]

{
  "mcpServers": {
    "kastell": {
      "args": [
        "-y",
        "kastell"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "kastell": {
      "args": [
        "-y",
        "kastell"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: HETZNER_TOKEN (Hetzner Cloud API token (optional — only for Hetzner servers)), DIGITALOCEAN_TOKEN (DigitalOcean API token (optional — only for DigitalOcean servers)), VULTR_TOKEN (Vultr API token (optional — only for Vultr servers)), LINODE_TOKEN (Linode API token (optional — only for Linode servers)). The author declared them in the registry entry; get the values from the project itself.