Allows management of MySQL databases through ISPConfig, including listing, creating, and deleting databases.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ispconfig-mcp list all DNS zones"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for ISPConfig 3 — manage DNS zones, mail domains, websites, databases, FTP users, cron jobs, and more through AI assistants like Claude.
DNS Management — zones, A/AAAA/CNAME/MX/NS/TXT/SRV/PTR records
Mail Management — domains, mailboxes, aliases, forwards, catchall, spamfilter
Site Management — web domains, subdomains, alias domains
Database Management — create/delete MySQL databases
FTP & Shell Users — create and manage access accounts
Cron Jobs — schedule and manage cron tasks
Client Management — create/update/delete ISPConfig clients
Server Info — query server details by ID or IP
Generic API Call — escape hatch for any of the ~246 ISPConfig API methods
Server Migration — export/import DNS zones, mail domains, websites, databases between ISPConfig instances
Related MCP server: cPanel MCP Server
Node.js 18+
An ISPConfig 3 installation with the Remote API enabled
API user credentials (ISPConfig → System → Remote Users)
# Via npx (no install needed)
npx ispconfig-mcp
# Or install globally
npm install -g ispconfig-mcpclaude mcp add ispconfig -- npx ispconfig-mcpThen set environment variables in your shell or .env:
export ISPCONFIG_URL="https://your-server:8080"
export ISPCONFIG_USER="api_user"
export ISPCONFIG_PASSWORD="your_password"
# Optional: run without any create/update/delete/import tools
export ISPCONFIG_READONLY="true"
# Optional (NOT recommended): skip TLS verification for self-signed certs.
# Only affects this server's own connection, but you should use a valid
# certificate instead — credentials are sent over this connection.
# export ISPCONFIG_INSECURE="true"Add to your MCP config file:
{
"mcpServers": {
"ispconfig": {
"command": "npx",
"args": ["-y", "ispconfig-mcp"],
"env": {
"ISPCONFIG_URL": "https://your-server:8080",
"ISPCONFIG_USER": "api_user",
"ISPCONFIG_PASSWORD": "your_password"
}
}
}
}Log into ISPConfig panel → System → Remote Users
Create a new remote user with API access
Grant only the functions this integration needs — do not grant all.
The api_call escape hatch and the write tools can only reach methods this
remote user is permitted to use, so a narrow permission set is your main
guardrail. Combine with ISPCONFIG_READONLY=true for read-only use.
Use these credentials as ISPCONFIG_USER / ISPCONFIG_PASSWORD
Tool | Description |
| List all DNS zones |
| Get zone details by ID |
| Create a new zone |
| Update zone settings |
| Delete a zone |
| Get a record by type and ID |
| Add a DNS record (A, AAAA, CNAME, MX, TXT, etc.) |
| Update a DNS record |
| Delete a DNS record |
Tool | Description |
| List all mail domains |
| Get mail domain details |
| Create a mail domain |
| Delete a mail domain |
| Get mailbox details |
| Create a mailbox |
| Update mailbox settings |
| Delete a mailbox |
| Create a mail alias |
| Delete a mail alias |
| Create a mail forward |
| Delete a mail forward |
| Create a catchall |
| Add to spamfilter whitelist |
| Add to spamfilter blacklist |
Tool | Description |
| List all websites |
| Get website details |
| Create a website |
| Update website settings |
| Delete a website |
| Create a subdomain |
| Delete a subdomain |
| Create an alias domain |
| List FTP users |
| Create an FTP user |
| Update FTP user |
| Delete an FTP user |
| Create a shell user |
| Delete a shell user |
| List databases |
| Create a database |
| Delete a database |
| List cron jobs |
| Create a cron job |
| Update a cron job |
| Delete a cron job |
Tool | Description |
| Get client details |
| Create a client |
| Update a client |
| Delete a client |
| Get server info |
| Find server by IP |
| Call any ISPConfig API method directly |
Tool | Description |
| Inventory all DNS/mail/sites on source — dry run, no changes |
| Export a DNS zone + all records as JSON bundle |
| Export a mail domain + mailboxes/aliases/forwards as JSON |
| Export a website + FTP/shell users/databases/cron as JSON |
| Export a client account + associated domains as JSON |
| Import a DNS zone bundle into destination instance |
| Import a mail domain bundle (config only — rsync maildir separately) |
| Import a website bundle (config only — rsync files separately) |
| Generate rsync/mysqldump commands for actual data transfer |
The MCP supports migrating accounts between ISPConfig instances. The workflow:
Plan — migrate_plan inventories everything on the source
Export — migrate_export_* dumps config as portable JSON bundles
Import — migrate_import_* recreates config on the destination
Data — migrate_data_commands generates rsync/mysqldump commands for actual files/mail/databases
For direct source→destination migration, configure both instances:
{
"mcpServers": {
"ispconfig": {
"command": "npx",
"args": ["-y", "ispconfig-mcp"],
"env": {
"ISPCONFIG_URL": "https://old-server:8080",
"ISPCONFIG_USER": "api_user",
"ISPCONFIG_PASSWORD": "password",
"ISPCONFIG_DEST_URL": "https://new-server:8080",
"ISPCONFIG_DEST_USER": "api_user",
"ISPCONFIG_DEST_PASSWORD": "password"
}
}
}
}Without ISPCONFIG_DEST_URL, export tools still work — you can save the JSON and import later.
DNS zones + all record types
Mail domains + mailboxes + aliases + forwards + catchall
Web domains + subdomains + alias domains
FTP and shell users
Database definitions
Cron jobs
Client accounts
The ISPConfig API manages configuration, not file data. These must be transferred separately:
Mail spools — rsync /var/vmail/domain/
Website files — rsync /var/www/domain/
Database content — mysqldump / pg_dump
The migrate_data_commands tool generates the exact commands needed.
Once connected, you can ask your AI assistant things like:
"List all DNS zones on my server"
"Add an A record for app.example.com pointing to 1.2.3.4"
"Create a mailbox info@example.com with 1GB quota"
"Add a mail forward from sales@example.com to team@example.com"
"Show me all websites and their domains"
"Create a cron job that runs /usr/local/bin/backup.sh every night at 2am"
"Find all zones missing SPF records"
"Export everything from the old server and show me a migration plan"
"Migrate the DNS zone for example.com to the new server"
"What rsync commands do I need to transfer mail data for example.com?"
git clone https://github.com/DayZAnder/ispconfig-mcp.git
cd ispconfig-mcp
npm install
npm run buildBSD 3-Clause — same license as ISPConfig 3.
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.
Inputs: method (required), params.
Create a new client
Inputs: params (required), reseller_id (required).
Delete a client
Inputs: client_id (required).
Get client details by ID
Inputs: client_id (required).
Update a client
Inputs: params (required), client_id (required), reseller_id (required).
Create a cron job
Inputs: params (required), client_id (required).
Delete a cron job
Inputs: cron_id (required).
List all cron jobs
Inputs: no named parameters.
Update a cron job
Inputs: params (required), cron_id (required), client_id (required).
Create a new database
Inputs: params (required), client_id (required).
Delete a database
Inputs: database_id (required).
List all databases
Inputs: no named parameters.
Add a DNS record to a zone
Inputs: type (required), params (required), client_id (required).
Delete a DNS record
Inputs: type (required), record_id (required).
Get a DNS record by type and ID
Inputs: type (required), record_id (required).
Update a DNS record
Inputs: type (required), params (required), client_id (required), record_id (required).
Create a new DNS zone
Inputs: ns (required), mbox (required), origin (required), client_id (required), +7 more.
Delete a DNS zone
Inputs: zone_id (required).
Get a DNS zone by ID
Inputs: zone_id (required).
List all DNS zones
Inputs: no named parameters.
Update an existing DNS zone
Inputs: params (required), zone_id (required), client_id (required).
Create an FTP user
Inputs: params (required), client_id (required).
Delete an FTP user
Inputs: user_id (required).
List FTP users
Inputs: no named parameters.
Update an FTP user
Inputs: params (required), user_id (required), client_id (required).
Create a mail alias
Inputs: params (required), client_id (required).
Delete a mail alias
Inputs: alias_id (required).
Create a catchall for a mail domain
Inputs: params (required), client_id (required).
Create a new mail domain
Inputs: params (required), client_id (required).
Delete a mail domain
Inputs: domain_id (required).
Get a mail domain by ID
Inputs: domain_id (required).
List all mail domains
Inputs: no named parameters.
Create a mail forward
Inputs: params (required), client_id (required).
Delete a mail forward
Inputs: forward_id (required).
Add email/domain to spamfilter blacklist
Inputs: params (required), client_id (required).
Add email/domain to spamfilter whitelist
Inputs: params (required), client_id (required).
Create a new mailbox
Inputs: params (required), client_id (required).
Delete a mailbox
Inputs: user_id (required).
Get a mail user/mailbox by ID
Inputs: user_id (required).
Update a mailbox
Inputs: params (required), user_id (required), client_id (required).
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.
Inputs: type (required), domain (required), dest_host (required), source_host (required), +1 more.
Export a client account with all associated domains as a migration bundle
Inputs: client_id (required), include_secrets.
Export a DNS zone with all its records as a migration bundle (JSON).
Inputs: zone_id (required), include_secrets.
Export a mail domain with all mailboxes, aliases, forwards, and catchall as a migration bundle
Inputs: domain_id (required), include_secrets.
Export a web domain with FTP users, shell users, databases, cron jobs, and subdomains as a migration bundle
Inputs: domain_id (required), include_secrets.
Import a DNS zone migration bundle into the destination ISPConfig instance. Requires ISPCONFIG_DEST_URL to be configured.
Inputs: bundle_json (required), dest_server_id (required), dest_client_id.
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.
Inputs: bundle_json (required), dest_server_id (required), dest_client_id.
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.
Inputs: bundle_json (required), dest_server_id (required), dest_client_id.
Generate a migration plan: inventory what exists on the source. Does NOT make any changes.
Inputs: scope (required).
Compare source and destination ISPConfig instances after migration. Requires ISPCONFIG_DEST_URL.
Inputs: scope (required).
Get server information
Inputs: server_id (required), section.
Find server by IP address
Inputs: ip (required).
Create a shell user
Inputs: params (required), client_id (required).
Delete a shell user
Inputs: user_id (required).
Create a web alias domain
Inputs: params (required), client_id (required).
Create a new website/web domain
Inputs: params (required), client_id (required).
Delete a web domain
Inputs: domain_id (required).
Get a web domain by ID
Inputs: domain_id (required).
List all web domains/sites
Inputs: no named parameters.
Update a web domain
Inputs: params (required), client_id (required), domain_id (required).
Create a subdomain
Inputs: params (required), client_id (required).
Delete a subdomain
Inputs: subdomain_id (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 62 tools
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.
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.
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.
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.
Web hosting your AI runs itself over MCP: deploy sites, Next.js, Postgres, domains. EU servers.
Agent-first web hosting: deploy sites, apps, databases and domains over MCP.
MCP-ready hosting provider for Minecraft, BungeeCord, TeamSpeak, VPS and many other game servers.
Manage your Servera hosting over MCP: VPS/VDS, DNS, firewall, backups, SSL, billing, tickets.
