Skip to main content
Glama
hl9020

mcp-all-inkl

by hl9020

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
kas_dnsA

Manage DNS records (A, AAAA, CNAME, MX, TXT, SRV...). IMPORTANT: zone_host MUST end with a trailing dot (e.g. "example.com." NOT "example.com"). Actions:

  • list: params {zone_host} - list all DNS records of a zone

  • create: params {record_aux: "0"} - record_aux must be a STRING not a number (e.g. "0"), record_name="" for zone root

  • update: params {record_id, ...fields} - modify a record (get record_id from list)

  • delete: params {record_id} - delete a record

  • reset: params {zone_host} - reset zone to defaults Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_domainB

Manage domains. Actions:

  • list: no params - list all domains

  • list_tlds: no params - available TLDs

  • create: params {domain_name, domain_tld, domain_path, ssl_proxy, redirect_status}

  • update: params {domain_name, ...fields}

  • delete: params {domain_name}

  • move: params {domain_name, target_kas_login} Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_subdomainA

Manage subdomains. Actions:

  • list: no params - list all subdomains

  • create: params {subdomain_name, domain_name} - e.g. subdomain_name="www", domain_name="example.com"

  • update: params {subdomain_name, ...fields} - may fail with "in_progress" right after creation, retry after a few seconds

  • delete: params {subdomain_name}

  • move: params {subdomain_name, target_kas_login} Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_databaseA

Manage MySQL databases. Actions:

  • list: no params - list all databases

  • create: params {database_password} - name is auto-generated

  • update: params {database_name, database_login, ...fields} - database_login required (same value as database_name), e.g. database_comment, database_password

  • delete: params {database_name, database_login} - database_login required (same value as database_name) Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_mailA

Manage email: mailboxes, forwards, mailing lists, filters. Actions:

  • list/create/update/delete: mailboxes (params: mail_login, mail_password, ...)

  • list_forwards: list all email forwards

  • create_forward: params {local_part, domain_part, target_0, target_1, ...} - target_N are the forward destinations (numbered from 0), e.g. target_0="user@example.com"; may fail with "fetch failed" on first attempt, retry once

  • update_forward: params {mail_forward, target_0, target_1, ...} - mail_forward is the full address e.g. "alias@example.com"; note: update may fail with "in_progress" right after creation, retry after a few seconds

  • delete_forward: params {mail_forward} - mail_forward is the full address e.g. "alias@example.com"

  • list_lists/create_list/update_list/delete_list: mailing lists

  • list_filters/add_filter/delete_filter: mail filters Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_cronjobA

Manage cronjobs. Actions:

  • list: no params - list all cronjobs

  • create: params {protocol, http_url, minute, hour, day_of_month, month, day_of_week} - protocol="https"|"http", http_url without protocol prefix, time values like crontab (* for every)

  • update: params {cronjob_id, ...fields}

  • delete: params {cronjob_id} Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_sslB

Manage SSL certificates. Action: update - params {domain_name, ssl_certificate_sni_crt, ssl_certificate_sni_key, ssl_certificate_sni_bundle} Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_accountA

Manage KAS accounts and settings. Actions:

  • list: list all accounts

  • get_resources: resource limits and usage

  • get_settings: account settings

  • get_server_info: server information (PHP versions, MySQL, OS)

  • create/update/delete: account management

  • update_settings/update_superuser: change settings Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

kas_systemC

Sessions, disk space, traffic. Actions:

  • create_session: create new auth session

  • get_space: disk space overview

  • get_space_usage: detailed space usage per directory

  • get_traffic: traffic statistics Optional params for all tools: "pick" (array of field names to return, reduces tokens) and "filter" (object to match, e.g. {"record_type":"MX"} returns only matching entries).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct hosting resource (SSL, cronjob, DNS, domain, subdomain, database, mail, account, system), so there is no ambiguity about which tool to select for a given task. Even related tools like domain and subdomain are clearly separated by resource type.

Naming Consistency5/5

All tools follow a consistent 'kas_<resource>' snake_case pattern, and actions within tools use predictable verb_noun conventions (list, create, update, delete). There are no mixed casing styles or vague tool names.

Tool Count5/5

9 tools is well-scoped for a hosting management server, covering all major resource areas without fragmentation or bloat. Each tool earns its place, and the count falls comfortably within the ideal 3-15 range.

Completeness4/5

The server provides full CRUD coverage for most resources (cronjobs, DNS, domains, subdomains, databases, mail) plus account and system monitoring. The only notable gap is that SSL only supports update (no create/list/delete), which may be acceptable depending on the provider's workflow, but is a minor limitation.

Maintenance

ActivityInactive
ResponsivenessNo issues