Skip to content
AI & automation

AI-managed servers: AI console, MCP & API

Manage VPSnet servers, domains, and DNS with AI — from the console built into your panel, from your own AI tools via MCP, or from scripts via the REST API.

Get startedSee pricing
Three ways in

One capability set, three ways to use it

Choose the way you work. Each connection has its own permissions; only the free AI allowance stays in the panel.

Free in panel

AI console in the VPSnet panel

Open your server in the VPSnet panel and say what you need in plain words — the assistant and the built-in generators are simply there, nothing to install. The assistant does the work on the machine itself, not just the talking. It works with Cloud VPS, VPS, Firecracker microVMs, Firecracker Functions and supported Windows Server machines.

Your AI account

ChatGPT, Claude, Gemini and Grok

Use your own AI conversation to diagnose and manage existing VPSnet services. Choose access during VPSnet sign-in. Developer tools can also use the existing vpsnet-mcp package with an API key.

Open AI connections

Paid key

REST API for scripts and automation

Everything the assistant can do, your own code can do too — at api.vpsnet.com. You create the access key in the panel and decide whether it may only look or also make changes. The full list of commands is published as an OpenAPI 3.0 file covering both the open parts and the ones your key unlocks, so tools like Postman set themselves up from it. Asking our AI model questions from outside the panel is a paid extra with its own key.

OpenAPI specification (v1)

Connect your own AI account

Open AI connections in your VPSnet account, choose your AI and follow its setup steps. Sign in to VPSnet to select your services and permissions, then return to your AI conversation.

01

ChatGPT

In Plugins, choose + → Add custom MCP server. Name it VPSnet, paste the address, select OAuth and Create as a plugin.

Open AI connections

02

Claude

In Connectors, choose + Add → Add custom connector. Name it VPSnet and paste the address. Choose Sign in now and Register automatically for the OAuth client.

Open AI connections

03

Gemini

In Connected Apps, choose Add a custom app, paste the address and click Next. Custom apps currently require an eligible personal account in the US, English, age 18+ and Keep Activity enabled. If the option is missing, this browser connection is not available for your account.

Open AI connections

04

Grok

Choose New Connector → Custom. Name it VPSnet, paste the address and continue with OAuth sign-in.

Open AI connections

05

What access does my AI receive?

You choose the services and permissions. File access and Linux commands need separate permission; Windows guest commands are not supported by this connector. Network permissions cover your account networks. Revoke access at any time by selecting Disconnect in AI connections.

06

Do I need a model API key?

No. You use your own AI account under that provider’s terms and limits. VPSnet sign-in grants access to your existing services. This does not connect your subscription to the VPSnet AI assistant, and the connector does not make purchases.

Capabilities

Automation with your VPSnet API key

The tool set spans your whole account — servers, domains, DNS, backups, Functions, and billing.

  • Order new services and start, stop, restart, or reinstall the OS on existing ones
  • Change plans and resources, calculate costs, set auto-renew, and renew services
  • Manage DNS zones and records with DNSSEC, templates, zone import/export, and diagnostics
  • Check availability, register, transfer, and renew domains; manage contacts, nameservers, and glue records
  • Create backups and snapshots, roll back, and request paid restores from off-node backups
  • Create, update, and invoke Firecracker Functions with logs, output, and cost visibility
  • List invoices and payments, and review login and management history
  • Manage SSH keys, API keys, rDNS, hostname, root password, IPv6, and extra settings

Capabilities depend on the selected surface and current permissions. The portal free AI allowance is limited to authenticated control-panel workflows. MCP and REST use explicit API-key scopes; model inference outside the panel is paid and inference-only.

Setup

Developer setup: MCP and REST API

  1. 1

    Create an API key

    In the VPSnet control panel, open Account > API Keys and generate a key. Choose a read-only or full-access scope; keys can be IP-restricted and given an expiration date.

  2. 2

    Add the MCP server to your AI tool

    Add the configuration on the right to Claude or any MCP-compatible assistant or IDE. The server installs with npx -y vpsnet-mcp and authenticates with your API key.

  3. 3

    Or call the REST API directly

    Send requests to api.vpsnet.com with the X-API-KEY header. The OpenAPI 3.0 specification documents public and API-key-protected endpoints, and dynamic-DNS updater tokens cover ddclient-style record updates. openapi-v1.yml

MCP configuration
{
  "mcpServers": {
    "vpsnet": {
      "command": "npx",
      "args": ["-y", "vpsnet-mcp"],
      "env": { "VPSNET_API_KEY": "your_api_key_here" }
    },
    "ssh": {
      "command": "npx",
      "args": ["-y", "mcp-server-ssh"]
    }
  }
}
Specifications

AI, MCP & API at a glance

AI consoleBuilt into the panel for Cloud VPS, VPS, Firecracker microVMs, Firecracker Functions, and supported Windows Server machines — no separate AI setup
MCP transportstdio (standard MCP transport) — install with npx -y vpsnet-mcp
MCP toolsContinuously updated catalogue for service, domain, DNS, snapshot, restore, Managed Applications, Functions, and on-demand server management
AuthenticationAPI key sent in the X-API-KEY header; key format is a vpsnet_ prefix plus a base64url token
ScopesRead-only or full-access keys, plus granular domain and DNS scopes such as domains:read, domains:order, dns:read, dns:write, and dnssec:manage
Paid operationsPaid domain actions require paid operations enabled on the key, spend caps, and idempotency keys
Rate limit60 requests per minute; API keys support IP restrictions and expiration dates
REST APIBase URL api.vpsnet.com; OpenAPI 3.0 specification at /openapi-v1.yml covers public /public/* and API-key-protected /api/v1/* endpoints
Dynamic DNSddclient-compatible dynamic-DNS updater tokens and ACME DNS-01 tokens, restrictable to source IP/CIDR allowlists
SSH accessPairs with the mcp-server-ssh MCP server for direct SSH, SFTP, and key generation inside your servers
FAQ

AI, MCP & API questions, answered

01

Can the VPSnet AI Assistant really manage servers?

Yes. It is designed to perform real server-side work, not only answer questions: inspect system state, run commands, install packages, configure services, edit files, troubleshoot errors, prepare deployments, create or update web pages, generate scripts, and automate maintenance tasks — then summarize what changed.

02

Do I need to set anything up to use the AI console?

No. The AI console is integrated in the VPSnet panel, so no separate AI setup is needed. It is available on Cloud VPS, VPS, Firecracker microVMs, Firecracker Functions, and supported Windows Server machines. If you prefer your own AI tools, you can use MCP directly instead.

03

Do you support MCP integration?

Yes. The vpsnet-mcp NPM package provides API-driven tools for VPSnet management, so any MCP-compatible AI assistant can order, configure, and manage services through VPSnet APIs. It pairs with mcp-server-ssh for direct SSH access where appropriate.

04

Do you provide API access for automation?

Yes — full API access with read-only or full-access scopes, covering all management operations. API keys can be IP-restricted with expiration dates, and the rate limit is 60 requests per minute. The same capabilities are also available through the vpsnet-mcp package for AI-powered automation.

05

Can AI manage my domains and DNS too?

Yes. Full domain and DNS management is available via the vpsnet-mcp MCP server and the REST API, with granular API-key scopes like domains:read, domains:order, dns:write, and dnssec:manage. Paid domain actions additionally require paid operations enabled, spend caps, and idempotency keys.

06

Is it safe to let AI work on my server?

AI can make mistakes, so review its actions before relying on them in production. The assistant works inside your service context and should be treated like an automation operator with server access. Premium AI usage is billed according to provider-reported usage and is visible in the control panel where enabled.

Resources

Documentation & developer resources

Everything you need to build against VPSnet — the OpenAPI spec and in-panel API reference, the MCP packages for AI tools, and an AI-readable overview to ground your assistant.

API documentation

MCP packages

AI-readable overview

By browsing the VPSnet.com website, you agree to the rules for the use of cookies.More