websupport-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBSUPPORT_API_KEY | Yes | The API key (pair identifier) for Websupport API access. | |
| WEBSUPPORT_API_SECRET | Yes | The API secret used for HMAC-SHA1 signing. | |
| WEBSUPPORT_ALLOW_WRITE | No | Set to '1' to register write tools. | off |
| WEBSUPPORT_API_BASE_URL | No | Base URL for the selected market. | https://rest.websupport.sk |
| WEBSUPPORT_ACCEPT_LANGUAGE | No | Language preference: en_us, sk, cs_cz, or hu. | en_us |
| WEBSUPPORT_ALLOW_DESTRUCTIVE | No | Set to '1' to register destructive tools. | off |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ws_auth_checkA | Verify that the configured Websupport API key and secret authenticate successfully. Returns {verified: true} on success. Use this first when diagnosing 401 errors. |
| ws_dns_zone_getA | Get the DNS zone attached to a service. |
| ws_dns_record_listA | List DNS records in a service zone, with paging and server-side filtering. Returns the API pagination envelope unflattened. |
| ws_ftp_account_listA | List FTP accounts on a hosting service. Passwords are never returned — the API response schema has no password field. |
| ws_ftp_account_getA | Get one FTP account by id. The password is never returned. |
| ws_user_getA | Get the account record: id, contact details, billing profiles, market and currency. SENSITIVE — the response includes the billing address, email address, phone number, and a verifyUrl containing a live account-verification key. Do not echo the full response to the user or store it; read the specific field needed. |
| ws_service_listA | List the account's services (hosting, domains, VPS and so on). Returns the v1 envelope {items, pager}. Service ids from here are the candidates for the v2 tools' |
| ws_service_getA | Get one service by id, including its type, status and expiry. Use ws_service_list first to find the id. |
| ws_zone_listA | List the DNS zones on the account. For the records inside a zone use the v2 tool ws_dns_record_list — v1 record CRUD is deprecated and deliberately not exposed. |
| ws_zone_getB | Get one DNS zone by domain name. |
| ws_hosting_listA | List the hosting services on the account. |
| ws_hosting_getA | Get one hosting service by id or uuid, including its package, limits and current usage. |
| ws_hosting_vhost_listA | List the virtual hosts (domains) served by a hosting service. |
| ws_hosting_vhost_getA | Get one virtual host by id, including its document root and domain configuration. |
| ws_hosting_statsA | Usage statistics for a hosting service. |
| ws_db_listA | List the databases on a hosting service. |
| ws_db_getA | Get one database by id, including its name, type and connection details. |
| ws_db_users_listB | List the database users on a hosting service. |
| ws_db_statsB | Usage statistics for one database. |
| ws_mailbox_listA | List the mailboxes on a hosting service. |
| ws_mailbox_getA | Get one mailbox by id, including its address, quota and forwarding configuration. |
| ws_mail_statsA | Mail storage statistics for a hosting service. Supply |
| ws_vps_listB | List the VPS instances on the account. |
| ws_vps_getA | Get one VPS by id or name, including its specification, IP addresses and power state. |
| ws_vps_statsA | Usage statistics for a VPS. |
| ws_vps_vncA | Get VNC console access details for a VPS. SENSITIVE — the response may carry a one-time console URL or session credential that grants direct machine access. Hand it to the user who asked for it and nothing else: do not log it, do not repeat it in a summary, and treat it as expiring. |
| ws_invoice_listA | List the account's invoices with their amounts, dates and payment status. Paying an invoice is deliberately out of scope for this server. |
| ws_invoice_getA | Get one invoice by id, including line items, totals and payment status. Use ws_invoice_pdf for the document itself. |
| ws_invoice_pdfA | Fetch an invoice as a PDF. |
| ws_vps_snapshot_listA | List the snapshots taken of a VPS, with their names and creation times. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
Each tool targets a distinct resource-action pair (e.g., list vs. get for hosting, databases, mailboxes, VPS, invoices). Even similar-sounding tools like ws_dns_zone_get and ws_zone_get differ by lookup key (service vs. domain), and ws_service_get vs. ws_hosting_get are clearly scoped by description.
All tools follow the consistent ws_verb_noun snake_case pattern (e.g., ws_dns_record_list, ws_hosting_vhost_get, ws_vps_snapshot_list). No style mixing or vague verbs.
With 30 tools, the surface is heavily over-populated for a typical MCP server. While the scope spans many resource types (DNS, FTP, hosting, DBs, mail, VPS, invoices), the count exceeds the 'heavy' 16-25 band and feels excessive even for a broad control-panel API.
The tool set is almost entirely read-only; there are no create, update, or delete operations for any resource (DNS records, FTP accounts, databases, mailboxes, VPS snapshots, etc.). The descriptions explicitly exclude actions like paying invoices and v1 record CRUD, leaving significant gaps for an expected management surface.