Skip to main content
Glama

allinkl-mcp

MCP-Server für die All-Inkl KAS-API — DNS, Domains, Subdomains, Mail-Postfächer, Mail-Weiterleitungen und Datenbanken verwalten, plus DB-Dump via SSH+mysqldump.

Die KAS-API kann Datenbanken nur anlegen/löschen — kein Dump. Deshalb läuft database_dump über SSH auf dem KAS-Paket.

Setup

cd ~/Projects/allinkl-mcp
pnpm install
cp .env.example .env      # dann .env ausfüllen
pnpm build

.env:

  • KAS_LOGIN — Account-Nummer, z.B. wXXXXXX

  • KAS_AUTH_DATA — API-Passwort (KAS → Tools → API, nicht das Login-Passwort)

  • KAS_SSH_HOST — Host-Alias aus ~/.ssh/config, der auf die KAS-Shell führt (für database_dump)

Related MCP server: dynadot-mcp

Erstmal testen (ohne MCP)

pnpm kas get_databases
pnpm kas get_dns_settings '{"zone_host":"example.com"}'

Der erste Call ist der echte Test der SOAP-Signatur — falls KAS meckert, justieren wir src/kas/client.ts (Param-Name / Response-Unwrap).

In Claude Code einbinden

{
  "mcpServers": {
    "allinkl": {
      "command": "node",
      "args": ["/path/to/allinkl-mcp/dist/index.js"]
    }
  }
}

Sicherheit (wichtig — geteilter Produktiv-Account)

  • Read-only per Default. add/update/delete sind gesperrt, bis KAS_ALLOW_WRITES=1 gesetzt ist (dann MCP neu starten). Reads + database_dump gehen immer.

  • kas_raw: nur get_*-Actions ohne Flag; alles andere braucht Writes on.

  • DB-Passwörter werden in database_list geschwärzt (opt-in via reveal_passwords: true).

  • Calls werden serialisiert (kein Flood-Race), Flood-Fehler werden einmal automatisch wiederholt, SOAP-Calls haben Timeout.

Verifizierungs-Status der Schreib-Params:

  • DNS add/update/delete — ✅ live verifiziert (add setzt automatisch den von KAS geforderten Trailing-Dot auf die Zone).

  • Übrige Writes (subdomain / mail / database / ftp / cronjob / domain / ssl) — ⚠️ nicht live verifiziert. Feldnamen sind an hl9020/mcp-all-inkl ausgerichtet (s.u.), aber ungetestet. Vor erstem Einsatz an einem unkritischen Objekt prüfen.

Alle Listen-Tools akzeptieren optional pick (nur diese Felder) und filter (z.B. {"record_type":"MX"}) zum Token-Sparen.

Tools (50)

Bereich

Tools

DNS

dns_list dns_add dns_update dns_delete dns_reset

Domains

domain_list domain_tld_list domain_add domain_update domain_delete domain_move

Subdomains

subdomain_list subdomain_add subdomain_update subdomain_delete subdomain_move

Mail

mail_list/add/update/delete, mailforward_list/add/update/delete, mailinglist_list/add/delete, mailfilter_list

Datenbanken

database_list database_add database_update database_delete database_dump (SSH)

FTP

ftp_list ftp_add ftp_update ftp_delete

Cronjobs

cronjob_list cronjob_add cronjob_update cronjob_delete

SSL

ssl_update

Account/System (read)

account_list account_resources account_settings server_info system_space system_space_usage system_traffic

Escape

kas_raw (beliebige Action, inkl. Account-Writes; unter Write-Guard)

Credits

Param-Namen für die Write-Actions und die pick/filter-Idee sind hl9020/mcp-all-inkl (MIT) entlehnt. Dieser Server ergänzt das um eine Safety-Schicht (read-only-Default, Delete- Confirm, Zonen-Allowlist, Audit-Log, Passwort-Redaction) und den SSH-DB-Dump.

Available Tools

25 tools
cronjob_addAdd cronjobC

Create a cronjob (add_cronjob). Params unverified against live API.

Inputs: cronjob_url, cronjob_hour, cronjob_type, cronjob_month, +5 more.

cronjob_deleteDelete cronjobA

Delete a cronjob (delete_cronjob). Requires confirm:true.

Inputs: cronjob_id (required), confirm.

cronjob_listList cronjobsC

List cronjobs (get_cronjobs).

Inputs: no named parameters.

cronjob_updateUpdate cronjobC

Update a cronjob (update_cronjob). Params unverified.

Inputs: cronjob_id (required), cronjob_url, cronjob_hour, cronjob_type, +6 more.

database_addAdd databaseA

Create a MySQL database (add_database). KAS auto-generates the db name and login.

Inputs: database_comment (required), database_password (required).

database_deleteDelete databaseA

Delete a MySQL database (delete_database). Requires confirm:true.

Inputs: database_login (required), confirm.

database_dumpDump database (SSH mysqldump)B

Export a MySQL database to a local .sql file via SSH + mysqldump. Requires an SSH host alias (KAS_SSH_HOST) that lands on the KAS shell.

Inputs: db_name (required), db_user (required), db_password (required), gzip, +1 more.

database_listList databasesA

List MySQL databases (get_databases). Passwords are redacted by default to avoid dumping all client DB credentials into the conversation.

Inputs: reveal_passwords.

dns_addAdd DNS recordC

Add a DNS record (add_dns_settings).

Inputs: zone_host (required), record_data (required), record_name (required), record_type (required), +1 more.

dns_deleteDelete DNS recordA

Delete a DNS record by id (delete_dns_settings). Requires confirm:true.

Inputs: record_id (required), confirm.

dns_listList DNS recordsC

Get DNS records for a zone (get_dns_settings).

Inputs: zone_host (required), record_id.

dns_updateUpdate DNS recordC

Update a DNS record by id (update_dns_settings).

Inputs: record_id (required), record_aux, record_data, record_name, +1 more.

ftp_addAdd FTP userB

Create an FTP user (add_ftpusers). KAS auto-generates the login prefix. Params unverified against live API.

Inputs: ftp_password (required), ftp_path, ftp_comment.

ftp_deleteDelete FTP userB

Delete an FTP user (delete_ftpuser). Requires confirm:true.

Inputs: ftp_login (required), confirm.

ftp_listList FTP usersB

List FTP users (get_ftpusers).

Inputs: no named parameters.

ftp_updateUpdate FTP userC

Update an FTP user (update_ftpuser). Params unverified.

Inputs: ftp_login (required), ftp_path, ftp_comment, ftp_password.

kas_rawRaw KAS API callA

Call any KAS action directly. action = kas_action string (e.g. get_cronjobs, add_ftpusers). params = KasRequestParams object. Writes need KAS_ALLOW_WRITES=1; delete_* also needs params.confirm=true.

Inputs: action (required), params.

mail_addAdd mail accountC

Create a mailbox (add_mailaccount).

Inputs: local_part (required), domain_part (required), mail_password (required), account_quota.

mail_deleteDelete mail accountA

Delete a mailbox (delete_mailaccount). Requires confirm:true.

Inputs: mail_login (required), confirm.

mailforward_addAdd mail forwardC

Create a mail forward / alias (add_mailforward).

Inputs: targets (required), local_part (required), domain_part (required).

mailforward_listList mail forwardsA

List mail forwards / aliases (get_mailforwards).

Inputs: no named parameters.

mail_listList mail accountsB

List all POP3/IMAP mailboxes (get_mailaccounts).

Inputs: no named parameters.

subdomain_addAdd subdomainC

Create a subdomain pointing at a path (add_subdomain).

Inputs: path (required), subdomain (required), domain_name (required), php_version, +1 more.

subdomain_deleteDelete subdomainA

Delete a subdomain (delete_subdomain). Requires confirm:true.

Inputs: subdomain_name (required), confirm.

subdomain_listList subdomainsA

List all subdomains (get_subdomains).

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (e.g., cronjob_add, database_delete). The resource prefix clearly separates domains, and actions are standard CRUD. There is no functional overlap between tools.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'resource_action' in snake_case (e.g., cronjob_add, ftp_list). The only exception is 'kas_raw', which is a special catch-all tool, but the overall pattern is uniform.

    Tool Count4/5

    25 tools cover multiple domains (cron, database, DNS, FTP, mail, subdomains) with 3-4 operations each. This is slightly above the typical 3-15 range but still well-scoped for a hosting management server.

    Completeness3/5

    Missing operations include mailforward_delete, mail_update, subdomain_update, and database_update. The raw API tool can compensate, but the defined set has notable gaps in lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers