Back to MCP Servers
🔌

kastelldev/kastell

Apache-2.0API key required

](https://glama.ai/mcp/servers/kastelldev/kastell) 📇 ☁️ 🏠 🍎 🪟 🐧 - Server security auditing and hardening toolkit. 413 security checks across 29 categories (SSH, Firewall, Docker, TLS, HTTP Header

TypeScriptAI & LLMs

Install

npx -y kastell

Required environment variables

HETZNER_TOKENSet in your MCP config
DIGITALOCEAN_TOKENSet in your MCP config
VULTR_TOKENSet in your MCP config
LINODE_TOKENSet in your MCP config

claude_desktop_config.json

claude_desktop_config.json
{
  "mcpServers": {
    "kastelldev-kastell": {
      "command": "npx",
      "args": [
        "-y",
        "kastell"
      ],
      "env": {
        "HETZNER_TOKEN": "<YOUR_HETZNER_TOKEN>",
        "DIGITALOCEAN_TOKEN": "<YOUR_DIGITALOCEAN_TOKEN>",
        "VULTR_TOKEN": "<YOUR_VULTR_TOKEN>",
        "LINODE_TOKEN": "<YOUR_LINODE_TOKEN>"
      }
    }
  }
}

Add this to your Claude Desktop config file. Find it at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.

What this does

kastelldev/kastell exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation. That makes it useful when you want Claude to reach into other AI providers and LLM tooling without copy-pasting context every turn.

Requirements

This server needs the following environment variables to be set before it can run:

HETZNER_TOKEN
DIGITALOCEAN_TOKEN
VULTR_TOKEN
LINODE_TOKEN

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Common use cases

  • Delegate reasoning to a different model or LLM provider from a Claude session
  • Pull live model documentation, rate limits, or usage data into context
  • Chain Claude with another agent or evaluation pipeline