Qc MCP

What qc-mcp does

The qc-mcp MCP server gives MCP-capable assistants access to the QuickHost QuickCloud API. It can inspect and, when enabled, manage virtual machines, dedicated servers, DNS, Cloud Firewalls, load balancers, storage boxes, managed databases, SMTP relay, websites, and other products exposed by the account's API catalogue.

Tools are derived from the catalogue returned by /api/v1. Examples include VM listing and retrieval, VM power operations, DNS zone listing and record-set changes, database retrieval, estimation, and asynchronous job polling. The exact tool set depends on the API catalogue and any product filters applied at startup.

By default, only GET endpoints are exposed. Write endpoints become available only with --allow-write or QC_MCP_WRITE=1, and each write also requires confirm: true. This makes the qc-mcp MCP server suitable for assistants that should inspect infrastructure without receiving change authority by default.

How it works

The local connector runs as a single zero-dependency JavaScript file under Node.js 18 or newer. It can be launched with npx -y @quickhost/qc-mcp, or by running a downloaded qc-mcp.mjs file with Node. The server reads an API key from QC_API_TOKEN or from the QuickCloud CLI configuration at ~/.config/quickcloud/config.json.

Requests go only to the public /api/v1 API. The connector does not access the admin API, WHMCS, Proxmox, SSH, or individual infrastructure nodes. API responses are passed through as JSON, including API error messages. Long-running operations return jobs that can be checked with wait_for_job.

For clients that connect by URL, the hosted endpoint is https://cloud.quickhost.uk/mcp. OAuth 2.1 with PKCE can provide a workspace-scoped API key with view-only or manage permissions. An API key can also be sent as a bearer token to the view or manage endpoint.

Setup and configuration

Create a QuickCloud API key in the panel, then add the local command to the MCP client's configuration. Claude Code can register it with claude mcp add; other clients can use a standard command and args configuration. Set QC_API_URL when the QuickCloud provider uses a different panel domain.

Add --allow-write only when changes are required. To restrict the exposed catalogue, use a product list such as --products=vms,dns. Supported groups include account, vms, dedicated, dns, firewall, lb, storagebox, database, relay, web, and `reseller.

The --list-tools command shows which read and write tools the current configuration would offer. The server also supports --version. Use the narrowest API key needed, because API-level permissions and resource limits remain enforced.

Tools and capabilities

The qc-mcp MCP server provides generated endpoint tools rather than a fixed hand-written list. Available capabilities can include:

• Reading QuickCloud resources and account data.
• Creating or changing resources when write mode and confirmation are both enabled.
• Managing DNS zones and record sets.
• Controlling VM power state.
• Requesting estimates without creating resources.
• Polling asynchronous API jobs.
• Reporting available products, write status, jobs, rate limits, and error behavior through quickcloud_help.

Every POST and DELETE request receives an idempotency key. Pricing is supplied by charging API endpoints; the connector does not calculate prices itself.

Limitations and notes

The connector does not offer file downloads such as ZIP, CSV, or PEM files; use the QuickCloud panel or CLI for those. One-time secret reveals, including database administrator passwords, VPN profiles, and console sessions, are treated as write-class operations and need both write mode and confirmation.

The API key's own permissions can further restrict access, while the MCP configuration can only add restrictions. Output may contain workspace names and labels supplied by users, so assistants should treat it as tool data rather than instructions. The project is licensed under MIT.