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.
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.
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.
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.
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.
Your own AI model in the VPSnet assistant
Connect your OpenRouter, OpenAI, Anthropic or Azure OpenAI account once, in Account → Own AI model. The VPSnet AI assistant then answers with your model on every server, in the web console, in Functions and in Applications. If you connect nothing, the VPSnet assistant works as before.
01How do I connect it?
In the control panel open Account → Own AI model, choose the provider, enter the model name and your API key, and press Test. Then confirm with your security code. From then on the assistant shows which model answers, and in any conversation you can switch to the VPSnet assistant.
02Which models work?
A model of your provider that accepts tools (function calling): the assistant works only through tools. The test sends your provider one short request and checks this before anything is saved.
03What do I need for Azure OpenAI?
Three values: the resource name (for example my-resource) or its address https://my-resource.openai.azure.com/openai/v1 (an address ending in .services.ai.azure.com works too); KEY 1 or KEY 2 from the resource’s Keys and Endpoint page; and the deployment name, which can differ from the model name. The deployment’s model must accept tools in Chat Completions; we tested gpt-5-mini. Only key authentication works (not Microsoft Entra ID), and only the public Azure cloud (not the government or China clouds). If Azure answers that a rate limit was reached, raise the deployment’s tokens-per-minute limit.
04What happens to my key and my data?
We store the key encrypted. Once saved it is shown to no one, not to you and not to our support; API keys, AI connections and support sessions can neither see nor use it. Everything the assistant works with goes to your provider: your questions, the conversation, what it reads on your server (command output, file contents), and in Functions and Applications the code or compose file. After a password change the model waits until you confirm it with your security code; until then the VPSnet assistant answers. You can remove the model at any time, and the key is deleted from VPSnet at once.
05What does it cost?
Nothing at VPSnet: answers of your model are not charged to your balance and do not use the free assistant allowance. Your provider bills you for the usage at its own prices. Create a separate key for VPSnet and set a spending limit for it at your provider.
Connect your own AI account
Open AI connections in your VPSnet account, choose your AI and follow its setup steps. The connection address is https://mcp.vpsnet.com/mcp. Sign in to VPSnet to select your services and permissions, then return to your AI conversation.
01ChatGPT
In Plugins, choose + → Add custom MCP server. Name it VPSnet, paste the address, select OAuth and Create as a plugin.
02Claude
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.
03Gemini
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.
04Grok
Choose New Connector → Custom. Name it VPSnet, paste the address and continue with OAuth sign-in.
05Can I connect another AI application?
Yes, if it can use a remote MCP server over Streamable HTTP with OAuth: add https://mcp.vpsnet.com/mcp and approve the connection in your VPSnet account. If the application asks for a client ID and secret, create them in AI connections (Other application). We have run ChatGPT, Claude, Gemini, Grok and Azure AI Foundry with VPSnet; other applications should work if they follow the MCP standard, but we have not tested them. VPSnet does not check other applications: on the approval screen, check the address your application returns to.
06How do I connect an Azure AI Foundry agent?
- In the VPSnet panel open Account → AI connections → Other application → Connect another application. Enter an application name and press Create application. Copy the Client ID and the Client secret: the secret is shown only once.
- In Azure AI Foundry add a Model Context Protocol (MCP) tool to your agent: server address https://mcp.vpsnet.com/mcp, authentication OAuth Identity Passthrough, the Client ID and Client secret from step 1, Auth URL https://api.vpsnet.com/oauth/mcp/authorize, Token URL and Refresh URL https://api.vpsnet.com/oauth/mcp/token, and scopes, for example services:read offline_access (add services:manage if the agent may start and stop servers).
- Foundry shows a Redirect URL. Add it to the application’s Callback addresses in AI connections and press Add.
- Ask the agent something. The first time, sign in to VPSnet, choose the servers and the permissions the agent gets, and approve. The connection lasts 30 days; then approve it again.
With each question the agent’s model receives the description of every tool it may use, so allowing only the tools it needs lowers the cost.
07What 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, while the server firewall applies only to the servers you select. Revoke access at any time by selecting Disconnect in AI connections.
08Do 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. Purchases are possible only if you separately allow them for this connection, with daily and monthly limits.
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, rDNS, hostname, root password, IPv6, and extra settings
- Networks: firewall, port forwarding, public addresses and their rDNS, private networks, load balancers, VPN
Capabilities depend on the selected surface and current permissions. The portal free AI allowance is limited to authenticated control-panel workflows. The hosted MCP uses OAuth with no API key; REST and the local (stdio) MCP use explicit API-key scopes; model inference outside the panel is paid and inference-only.
Developer setup: MCP and REST API
- 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
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
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
{
"mcpServers": {
"vpsnet": {
"command": "npx",
"args": ["-y", "vpsnet-mcp"],
"env": { "VPSNET_API_KEY": "your_api_key_here" }
},
"ssh": {
"command": "npx",
"args": ["-y", "mcp-server-ssh"]
}
}
}AI, MCP & API at a glance
| AI console | Built into the panel for Cloud VPS, VPS, Firecracker microVMs, Firecracker Functions, and supported Windows Server machines — no separate AI setup |
|---|---|
| MCP transport | Your AI account: https://mcp.vpsnet.com/mcp (OAuth, no key). Developer tools: stdio, npx -y vpsnet-mcp with an API key |
| MCP tools | Continuously updated catalogue for service, networking, domain, DNS, snapshot, restore, Managed Applications, Functions, and on-demand server management |
| Authentication | API key sent in the X-API-KEY header; key format is a vpsnet_ prefix plus a base64url token |
| Scopes | Read-only or full-access keys, plus granular permissions that narrow a key, such as services:read, domains:read, dns:write. For network functions (firewall, port forwarding, public addresses), networking:manage has to be added to the key separately |
| Paid operations | Actions that spend from your balance (orders, renewals, restores, Functions runs, AI inference) need paid operations switched on for the key, the matching paid permission, daily and monthly spend caps, and an idempotency key |
| Rate limit | 300 requests per minute per key by default, with lower limits on some operations; API keys support IP restrictions and expiration dates |
| REST API | Base URL api.vpsnet.com; OpenAPI 3.0 specification at /openapi-v1.yml covers public /public/* and API-key-protected /account/* and /order/* endpoints |
| Dynamic DNS | ddclient-compatible dynamic-DNS updater tokens and ACME DNS-01 tokens, restrictable to source IP/CIDR allowlists |
| SSH access | Pairs with the mcp-server-ssh MCP server for direct SSH, SFTP, and key generation inside your servers |
AI, MCP & API questions, answered
01Can 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.
02Do 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.
03Do 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.
04Do 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 each key may make 300 requests per minute by default (some operations have lower limits). The same capabilities are also available through the vpsnet-mcp package for AI-powered automation.
05Can 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. Registering, renewing and transferring domains also need paid operations switched on for the key, the matching paid permission, daily and monthly spend caps, and an idempotency key.
06Is 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.
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
- OpenAPI 3.0 specificationMachine-readable spec of the public /public/* and API-key-protected /account/* endpoints — import it into Postman, Insomnia, or a code generator.
- Managed Applications documentationProduct guide for VPSnet catalog apps (install, credentials, HTTPS, lifecycle) and links to per-app pages — not a generic developers hub. API contract is linked there for automation.
- API reference in your panelThe full human-readable endpoint documentation, live in the VPSnet control panel under Account > API Keys (sign-in required).
MCP packages
- vpsnet-mcp on NPMThe MCP server that gives Claude and other AI tools a continuously updated catalogue for your VPSnet account. Install with npx -y vpsnet-mcp.
- vpsnet-mcp source on GitHubSource code, issues, and changelog for the vpsnet-mcp server.
- mcp-server-ssh on NPMCompanion MCP server for direct SSH and SFTP work inside your servers — pairs with vpsnet-mcp.
- mcp-server-ssh source on GitHubSource code and issues for the companion SSH/SFTP MCP server.