Full Stack VPS
Create a VPS with its own database, a scoped API key and an MCP endpoint, so AI agents and your own code can drive it.
A Full Stack VPS is an ordinary Xuda VPS with three things attached at create time: a scoped API key that belongs to the machine, its own project database, and an MCP endpoint that exposes the platform capabilities you choose as callable tools. It is stored as a normal VPS with a flag, so every plain-VPS feature, firewall, resize, power, backups, the web route, works on it unchanged.
Xuda also has a separate deployment type called MCP Server, which puts a dedicated MCP endpoint in front of a project's API routes. That is a different product from the endpoint described here, which is built into the box itself.
Before you start
There is no free tier: a Full Stack VPS is billed hourly from its first hour, on any plan. Two things to decide before you click create, because both are fixed at create time:
- The shared server class is not available for this product. Picking one is refused before anything is provisioned. Choose Optimized, Performance or Large.
- Capabilities are chosen once. The Tools tab is read-only afterward. Decide the capability set in the wizard.
Create one
Open the Create flow
From the Create gallery, pick Full Stack App on VPS. The wizard has four steps: Power, Setup, Tools, Finalize Details. The Tools step is what a plain VPS wizard does not have.
Choose region and power
Pick a region, then a size. Optimized is the sensible starting point; Performance trades disk for memory per core; Large is for very large local disks. See Managed sizes and pricing for the full ladder.
Choose the operating system
A flat OS picker on Xuda's own farm hosting, or the full image and marketplace picker when the box provisions on DigitalOcean. Choose a clean operating system unless you have a reason not to.
Choose the capability groups
A grid of switches, all on by default, with Select all and Clear at the top. Each switch is a group of platform methods; the union of every group left on becomes the allowlist on the box's key. See Capability groups below for exactly what each one grants.
Name the box and create it
Automatic backups are an optional paid add-on here too. Press create and a progress view shows the real steps: initiating, issuing the API key, creating the server, setting the firewall and backup plan, connecting to the server, installing the toolchain, activating.
On Xuda's own farm hosting, cloud-init does not install Node, the CLI or Codex. A farm-hosted box still gets its key, database and MCP endpoint; you install the toolchain yourself if you want it on the machine. Which path you are on is visible at the Setup step: a flat OS list means the farm, the full image and marketplace picker means DigitalOcean.
Find the endpoint and the key
Open the box's Tools tab. The MCP endpoint card has a Copy button; copy it from there rather than typing one from memory. Below it, every enabled group is listed with the methods it granted, and anything you turned off shows in a Not enabled strip.
Open API Keys for the key named <box name> (full stack vps), the bearer token for the
endpoint. Suspending this key from that tab switches the box's whole tool surface off at once,
without touching the running machine or its data.
On a DigitalOcean-hosted box the same key is already on the machine, in
/root/xuda.config.js and as XUDA_API_KEY, XUDA_HOSTNAME and XUDA_AGENT_KEY in
/etc/profile.d/xuda.sh.
Point an agent at the box
Two ways, and they are not equivalent:
- From your own MCP client. Add a server with the Tools-tab URL and
Authorization: Bearer <key>. The platform registers one tool per method in the key's allowlist, plus one tool per box plugin, named<plugin>__<method>. - From inside Xuda. In Studio, add a tool of type Full Stack VPS to an agent and pick the box from the dropdown. Nothing but the box's identity is stored on the agent; the key is resolved server-side at run time.
Prefer the second option for an agent that lives in Xuda. Every action an agent takes on the box is written to the box's Logs tab.
Two safety behaviors are worth knowing: opening the first firewall port also opens port 22, so an agent cannot lock you out by accident, and an agent asking to close port 22 is refused outright.
Capability groups
Thirteen switches, expanding to a fixed set of platform methods. The Deploy & hosting card
names three SSH-over-WebSocket methods (vps_enable_ssh, vps_rotate_ssh_token,
vps_disable_ssh) that are not actually reachable with the box's key, so that group grants
eleven working methods rather than the fourteen it lists; manage SSH access from the box's
Overview tab instead. MCP server carries no methods of its own, it is the switch that
publishes everything else as MCP tools.
If the box will be handed to an autonomous agent, turn off what it has no business touching. Contacts, Email and Drive are the three most people scope out first, because they reach account-wide data rather than this server.
Access consents
A Full Stack VPS is treated as your machine, not Xuda's, so five features ask for consent the first time each is used, and all five are reviewable from Advanced:
Each grant and revoke is recorded with who and when. Revoking one does not affect the others.
Managed sizes and pricing
No membership plan gate, no per-capability or per-MCP-call fee: enabling all thirteen groups costs the same as enabling one.
Add-ons: automatic backups $10/mo plus $0.05/GB stored, dedicated IPv4 $2.50/mo plus a one-time $10 setup fee, Auto Diagnose $5/mo per server, farm block storage $0.10/GB/mo (rate only, see VPS for why you cannot create a volume from the dashboard yet).
The Tools tab says so in place: re-issuing the box's key with a different capability set is coming, not live. If you need a different surface today, create a new box, or suspend the key from API Keys as an immediate stop.
Next
For the plain-VPS tabs this product inherits unchanged, see Create and run a VPS. For putting a domain on the box, see Domains.