Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ISPCONFIG_URLYesThe URL of the ISPConfig server (e.g., https://your-server:8080)
ISPCONFIG_USERYesThe API user for ISPConfig
ISPCONFIG_DEST_URLNoURL of the destination ISPConfig server for migration
ISPCONFIG_INSECURENoSet to 'true' to skip TLS verification for self-signed certificates
ISPCONFIG_PASSWORDYesThe password for the ISPConfig API user
ISPCONFIG_DEST_USERNoAPI user for the destination ISPConfig server
ISPCONFIG_DEST_PASSWORDNoPassword for the destination ISPConfig API user

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
dns_zone_listA

List all DNS zones

dns_zone_getA

Get a DNS zone by ID

dns_record_getB

Get a DNS record by type and ID

dns_zone_addC

Create a new DNS zone

dns_zone_updateC

Update an existing DNS zone

dns_zone_deleteC

Delete a DNS zone

dns_record_addC

Add a DNS record to a zone

dns_record_updateC

Update a DNS record

dns_record_deleteC

Delete a DNS record

mail_domain_listA

List all mail domains

mail_domain_getB

Get a mail domain by ID

mail_user_getA

Get a mail user/mailbox by ID

mail_domain_addC

Create a new mail domain

mail_domain_deleteC

Delete a mail domain

mail_user_addC

Create a new mailbox

mail_user_updateC

Update a mailbox

mail_user_deleteC

Delete a mailbox

mail_alias_addC

Create a mail alias

mail_alias_deleteB

Delete a mail alias

mail_forward_addC

Create a mail forward

mail_forward_deleteB

Delete a mail forward

mail_catchall_addC

Create a catchall for a mail domain

mail_spamfilter_whitelist_addB

Add email/domain to spamfilter whitelist

mail_spamfilter_blacklist_addC

Add email/domain to spamfilter blacklist

web_domain_listA

List all web domains/sites

web_domain_getA

Get a web domain by ID

ftp_user_listA

List FTP users

database_listB

List all databases

cron_listA

List all cron jobs

web_domain_addC

Create a new website/web domain

web_domain_updateD

Update a web domain

web_domain_deleteB

Delete a web domain

web_subdomain_addC

Create a subdomain

web_subdomain_deleteB

Delete a subdomain

web_aliasdomain_addC

Create a web alias domain

ftp_user_addC

Create an FTP user

ftp_user_updateD

Update an FTP user

ftp_user_deleteB

Delete an FTP user

shell_user_addC

Create a shell user

shell_user_deleteC

Delete a shell user

database_addB

Create a new database

database_deleteC

Delete a database

cron_addC

Create a cron job

cron_updateC

Update a cron job

cron_deleteC

Delete a cron job

client_getA

Get client details by ID

server_getC

Get server information

server_get_by_ipB

Find server by IP address

client_addB

Create a new client

client_updateC

Update a client

client_deleteC

Delete a client

api_callA

Call any ISPConfig API method directly (escape hatch for methods not covered by other tools). NOTE: can invoke destructive operations; disabled when ISPCONFIG_READONLY=true.

migrate_export_dns_zoneA

Export a DNS zone with all its records as a migration bundle (JSON).

migrate_export_mail_domainA

Export a mail domain with all mailboxes, aliases, forwards, and catchall as a migration bundle

migrate_export_web_domainA

Export a web domain with FTP users, shell users, databases, cron jobs, and subdomains as a migration bundle

migrate_export_clientB

Export a client account with all associated domains as a migration bundle

migrate_planA

Generate a migration plan: inventory what exists on the source. Does NOT make any changes.

migrate_data_commandsA

Generate rsync/mysqldump commands needed to transfer actual data (files, mail, databases) between servers. These commands must be run manually — the MCP handles config only.

migrate_verifyA

Compare source and destination ISPConfig instances after migration. Requires ISPCONFIG_DEST_URL.

migrate_import_dns_zoneB

Import a DNS zone migration bundle into the destination ISPConfig instance. Requires ISPCONFIG_DEST_URL to be configured.

migrate_import_mail_domainA

Import a mail domain migration bundle into the destination ISPConfig instance. Creates domain, mailboxes, aliases, and forwards. NOTE: maildir data must be rsynced separately; redacted passwords must be reset.

migrate_import_web_domainA

Import a web domain migration bundle into the destination ISPConfig instance. Creates site, FTP/shell users, databases, cron jobs. NOTE: Website files and DB dumps must be transferred separately.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 62 tools

Disambiguation4/5

Most tools follow a clear resource-action pattern (web_domain_*, dns_zone_*, mail_user_*, ftp_user_*, etc.), so an agent can usually identify the right target. A few boundaries are less crisp: dns_record_get uses 'type and ID', api_call overlaps every method, and migrate_import_* can resemble normal create tools.

Naming Consistency4/5

The vast majority use consistent snake_case category_entity_action names, making the set highly navigable. Deviations like server_get_by_ip, api_call, and the migrate_export_* / migrate_import_* prefix pattern prevent a perfect score.

Tool Count2/5

62 tools is a very large surface for an MCP server, even though ISPConfig covers many subsystems; it will burden selection and context. The migration suite is cohesive, but the overall set could be trimmed or grouped.

Completeness2/5

Many areas lack full lifecycle coverage: alias domains only add, mail domains no update, mail users no list, DNS records no listing, shell users only add/delete, and clients no list. The api_call escape hatch masks gaps but delegates the work to raw API knowledge, so common agent workflows will still hit dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues