Qc MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 54 installs a week from npm. Last commit 12 Oct 2026.
QuickCloud hosting from your AI assistant: VMs, servers, DNS, firewalls and more. Read-only default.
We read the source, 4 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const chk = spawnSync(process.execPath, ['--check', tmp], { encoding: 'utf8' });
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const chk = spawnSync(process.execPath, ['--check', tmp], { encoding: 'utf8' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Qc MCP and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add qc-mcp -e 'QC_API_TOKEN=<QC_API_TOKEN>' -- npx -y @quickhost/qc-mcp
{
"mcpServers": {
"qc-mcp": {
"command": "npx",
"args": [
"-y",
"@quickhost/qc-mcp"
],
"env": {
"QC_API_TOKEN": "<QC_API_TOKEN>"
}
}
}
}
[mcp_servers.qc-mcp]
command = "npx"
args = ["-y", "@quickhost/qc-mcp"]
env = { QC_API_TOKEN = "<QC_API_TOKEN>" }
{
"mcpServers": {
"qc-mcp": {
"command": "npx",
"args": [
"-y",
"@quickhost/qc-mcp"
],
"env": {
"QC_API_TOKEN": "<QC_API_TOKEN>"
}
}
}
}
{
"servers": {
"qc-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@quickhost/qc-mcp"
],
"env": {
"QC_API_TOKEN": "<QC_API_TOKEN>"
}
}
}
}
Put your own value in place of
<QC_API_TOKEN> (Your QuickCloud API key (create one in the panel under API). A read-only or product-limited key is the safest to give an assistant).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
QC_API_URL (Panel origin. Only needed if your provider runs QuickCloud on their own domain (default https://cloud.quickhost.uk)), QC_MCP_WRITE (Set to 1 to allow the assistant to create and change things (equivalent to the --allow-write flag). Every write still asks for your confirmation).
Manage your Squish domains, DNS, hosting, backups and site files from your AI assistant.
Connect your AI assistant to YNAB. Read-only by default, with reversible opt-in writes.
Manage VeriTeknik servers, DNS, backups and support tickets from your AI assistant.
Manage HepCloud (Turkish cloud) servers and managed PostgreSQL from your AI assistant. OAuth 2.1.
Build and run a business from your AI assistant, with hosting, payments, email and more built in.
Browse, search, and discover MCP servers from your AI assistant
Manage Vozora VPS servers, SSH keys, firewalls, DNS and usage from an AI agent.
Read-only access to your VeloCapture leads, RFPs, contacts and drafts from an AI assistant.
Answers built from our own checks of this server.