DigitalOcean
DigitalOcean: droplets, volumes, snapshots, reserved IPs, DNS and managed databases — with the billing surprises made explicit.
About
DigitalOcean ships in the w6w first-party pack. It declares 15 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.digitalocean- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- DevOps & Infrastructure · Storage
Overview
DigitalOcean brings droplets, storage, DNS and managed databases into a workflow, with the billing surprises that catch people off guard made explicit rather than left to the invoice. Droplet actions cover the full lifecycle — create, power on or off, resize and delete — with the reversible, gentler operations chosen as the default over their permanent or forceful counterparts.
The app calls out costs that a plain API response would hide: a powered-off droplet still bills until it is archived, destroying a droplet leaves its volumes and snapshots behind still costing money, and a reserved IP bills precisely while it looks unused. Listing droplets counts how many are off but still billing, and deleting one requires acknowledging what it will orphan.
Beyond droplets, the app manages block storage volumes, snapshots, reserved IPs, DNS records and managed database clusters — stripping admin passwords out of database connection details before they ever reach a workflow’s data. DNS record creation catches the common mistake of accidentally doubling a fully-qualified domain name onto its zone.
Build with DigitalOcean
Three routes to the same 15 actions. The Workflow tab is generated from DigitalOcean's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Get the account
account-get The account behind this token and its resource LIMITS. Hitting a limit is a 422 on creation, which reads as a bad size or region rather than as a quota — and this is where the number is knowable in advance.
Get the account balance
billing-get Month-to-date usage and the account balance — the only billing figures the API exposes. Note the sign: a NEGATIVE balance means the account is in credit. There is no per-resource breakdown, so waste is found through the volume, snapshot and reserved-IP actions.
List database clusters
database-list Managed database clusters. The API's connection strings embed the ADMIN PASSWORD, so this returns the host, port and name separately and strips it — a full connection string in a workflow's data is a credential in a log.
Create a DNS record
domain-record-create Add a DNS record. The name is RELATIVE — giving `www.example.com` under `example.com` creates `www.example.com.example.com`, which the API accepts silently — so that form is refused here. Defaults to a 300-second TTL, because a TTL is how long a mistake lasts.
List DNS records
domain-record-list A domain's DNS records. The name is RELATIVE — the domain itself is `@`, never the fully-qualified form — so this returns the qualified name alongside, which is what a caller usually means.
Create a droplet
droplet-create Create a droplet. The response is a droplet that is NOT READY — status `new`, no IP yet — so a workflow that creates and then connects fails. Without SSH keys, DigitalOcean emails a plain-text root password and allows password logins.
Destroy a droplet
droplet-delete Destroy a droplet, which stops its charge. Its VOLUMES, SNAPSHOTS and RESERVED IP survive and keep billing — an unassigned reserved IP is the state that costs — so this counts what would be orphaned first.
Get a droplet
droplet-get One droplet, with its PUBLIC and PRIVATE addresses returned separately — indexing `networks.v4[0]` gets whichever came first, often the private one, and connecting to that from outside looks like a firewall problem.
List droplets
droplet-list The account's droplets. A droplet with status `off` is STILL BILLING — only destroying it stops the charge — so this counts them, because powering things down to save money is the commonest misunderstanding here.
Power a droplet
droplet-power Power a droplet on, shut it down gracefully, or CUT ITS POWER. `power_off` is pulling the plug and risks filesystem damage, so it is gated. And none of this stops the bill — only destroying a droplet does.
Resize a droplet
droplet-resize Resize a droplet. Including the DISK is PERMANENT — it can never be shrunk again, and neither can the price floor — so this defaults to the CPU-and-RAM-only form, which is reversible. The droplet must be off, and stays off afterwards.
List reserved IPs
reserved-ip-list Reserved IPs, counting the UNASSIGNED ones — which is the inverse of the usual rule: an assigned reserved IP is free and an unassigned one is charged hourly, and destroying a droplet creates that state automatically.
Snapshot a droplet
snapshot-create Take a snapshot — the only way back from destroying a droplet or resizing its disk. It bills per gigabyte per month FOREVER, and a snapshot of a running droplet is crash-consistent rather than clean.
List snapshots
snapshot-list Snapshots with their total size and age. They are charged per gigabyte per month, have NO EXPIRY, outlive whatever they were taken from, and nothing mentions them afterwards.
List volumes
volume-list Block storage volumes, counting the UNATTACHED ones — which bill per gigabyte forever and routinely outlive the droplets they were made for, because destroying a droplet does not destroy them.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying DigitalOcean's real ids.
{
"manifestVersion": "2",
"name": "digitalocean-example",
"steps": [
{
"id": "domain-record-create",
"uses": {
"app": "io.w6w.digitalocean",
"action": "domain-record-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"domain": "<domain>",
"type": "<type>",
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create a DNS record
performdomain-record-create -
Get the account
readaccount-get -
Get the account balance
readbilling-get -
List database clusters
searchdatabase-list -
List DNS records
searchdomain-record-list
+10 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for DigitalOcean, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to DigitalOcean. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "domain-record-create",
payload: {
domain: "<value>",
type: "<value>",
name: "<value>",
data: "<value>",
// ttl: "<value>",
// priority: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action domain-record-create --payload '{"domain":"<value>","type":"<value>","name":"<value>","data":"<value>"}'Give an AI agent DigitalOcean — without giving it DigitalOcean's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.digitalocean#domain-record-create",
"input": {
"domain": "<domain>",
"type": "<type>",
"name": "<name>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's DigitalOcean connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
DigitalOcean's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. DigitalOcean itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
DigitalOcean declares its own checks, so its health is a property of the app rather than something the host guesses at.
DigitalOcean status
Reads status.digitalocean.com, resolving every component through its GROUP — 15 components are called `Global` and 13 are called `FRA1`, so a name alone identifies nothing. Separates the API, which this app needs, from products in regions, which affect the resources.
Request budget
Reads DigitalOcean's real hourly request budget — 5,000 per TOKEN, shared by every automation using it. `RateLimit-Reset` is a Unix TIMESTAMP rather than a delay, which is the opposite of most of this pack.