VPSnet

What VPSnet MCP server does

The VPSnet MCP server gives MCP-compatible AI clients access to VPSnet.com customer services. Its toolset covers VPS lifecycle management, managed applications, networking, domains, certificates, account administration, and billing-related tasks. The repository describes more than 280 tools, so it is intended for accounts where an agent needs to inspect or change several VPSnet service areas rather than one isolated resource type.

Supported operations include starting, stopping, restarting, and reinstalling VPS instances; changing plans; ordering VPS instances; and managing reverse DNS records. DNS tools cover zones, records, DNSSEC, templates, import and export, and DDNS tokens. Domain tools support availability checks, contacts, registration, transfers, renewals, restoration quotes, and paid confirmations.

Managed application tools support catalog discovery, installation, health checks, events, logs, access configuration, resource-threshold settings, and typed lifecycle actions. The server also covers TLS certificates, Automatic SSL subscriptions, backups, invoices, API-key metadata, SSH-key provisioning, system status, and pricing.

How it works

The VPSnet MCP server can run as a local stdio service using an API key, or through VPSnet's remote OAuth endpoint at https://mcp.vpsnet.com/mcp. The remote connector uses customer consent, while VPSnet enforces permissions on each backend request. The remote profile includes scoped access for DNS, domains, certificates, public SSH keys, server recovery, and backup browsing.

Application changes are asynchronous. After an installation or lifecycle request, use the application installation and event tools to verify the resulting state. Health and log inspections create short-lived inspection jobs. Application installation and lifecycle changes require the relevant application permissions and an idempotency key.

Setup and configuration

Local use requires Node.js 20 or newer, an active VPSnet.com account, and an API key. VPSNET_API_KEY is the preferred per-launch credential. Alternatively, configure a directory containing .vpsnet-mcp-key or .mcp.json with VPSNET_CONFIG_DIR, or select one key file with VPSNET_API_KEY_FILE.

Without VPSNET_CONFIG_DIR, file lookup uses the process launch directory, not the package or installation directory. This matters when an editor launches the MCP process from a different working directory. Keep credential files out of source control. VPSNET_API_URL can override the URL configured in the relevant JSON file, subject to the server's HTTPS and trusted-host checks.

Remote clients use the VPSnet endpoint and customer authorization flow. The repository also documents client bundles and skills for supported remote integrations, while the npm package provides the local MCP server.

Tools and capabilities

• Manage VPS state, plans, operating-system reinstalls, orders, recovery, backups, and reverse DNS.
• Inspect and change managed applications, including access modes, health, events, logs, and resource display thresholds.
• Manage DNS zones, records, DNSSEC, templates, imports, exports, DDNS tokens, and domains.
• Handle certificates, Automatic SSL subscriptions, SSH keys, API-key metadata, billing, invoices, pricing, and account data.

Limitations and notes

Permissions differ by operation. Application reads require applications:read; installation and lifecycle changes require applications:manage. API-key creation, modification, and revocation remain session-only rather than MCP tools. Registry credential tools expose metadata only; token creation and rotation must occur in the VPSnet panel or direct REST API.

Managed application support follows VPSnet's product, operating-system, architecture, and runtime compatibility rules. Resource thresholds only highlight measurements and do not enforce limits, trigger actions, or change billing. External HTTPS entries record an existing customer-managed address; VPSnet does not configure or validate its DNS, certificate, or reverse proxy.