Connect DigitalOcean to Claude Code

Inspect droplets, managed databases, App Platform apps, Kubernetes clusters, load balancers, and billing. Add Toolspoke to Claude Code once and it can use 12 DigitalOcean actions. Your DigitalOcean credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install DigitalOcean and connect it

    Add DigitalOcean to a project in your Toolspoke workspace.

    Personal access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Personal access token
    Cloud control panel → API → Tokens → Generate New Token. A read-only token covers every operation here except reboot_droplet, which needs write. Scopes can be narrowed further per resource, droplet:read, app:read, database:read, kubernetes:read, load_balancer:read, billing:read and account:read are the full set these reads use.
  3. Choose what Claude Code may do

    All 12 actions start on. Switch off the one action that changes something in DigitalOcean, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the DigitalOcean actions that only read, so they are safe to try first.

  • List the account's droplets with each one's id, name, status, region, size, image and network addresses
  • List the App Platform apps in the account with each one's id, name, region, live deployment and spec

What Claude Code can do in DigitalOcean

11 actions read and one deletes or permanently changes something.

Reads

  • Get account

    Return the account this token belongs to, its email, team, status, and the droplet, volume and floating-IP limits it is allowed. Call it to confirm which account the connection reaches before acting on anything in it.

  • List droplets

    List the account's droplets with each one's id, name, status, region, size, image and network addresses. Call this first to get the numeric droplet id every other droplet action takes. Note that tag_name cannot be combined with name or type. DigitalOcean rejects the request rather than intersecting them.

  • Get droplet

    Fetch one droplet by id, including its region, size, attached volumes, backup and monitoring features, kernel, and every network interface with its addresses.

  • List droplet actions

    List the actions that have run against one droplet, newest last, with each action's type, status, and start and completion times. Use it to see whether a reboot finished, and to read the history of what has been done to a machine before doing anything else to it.

  • List databases

    List the account's managed database clusters with each one's engine, version, size, region, node count and status. The response carries each cluster's connection block, which includes the admin user's password, so it is recorded as a call but its body is never written to the audit log.

  • Get database cluster

    Fetch one managed database cluster by its UUID, engine and version, node count and size, region, maintenance window, firewall rules, and its connection details. Those connection details include the admin password in plain text, which is why this response is never written to the audit log.

  • List apps

    List the App Platform apps in the account with each one's id, name, region, live deployment and spec. The spec carries the app's environment variables, values typed SECRET come back encrypted, but everything else comes back as written, so this response is not kept in the audit log.

  • Get app

    Fetch one App Platform app, its full spec (services, workers, static sites, databases, routes and environment variables), its active deployment, and its default ingress hostname. The app id is always required; name is an extra filter DigitalOcean accepts alongside it, not a substitute for it. Environment variables are part of the spec, so this response is not written to the audit log.

  • List kubernetes clusters

    List the account's DOKS clusters with each one's id, name, region, Kubernetes version, VPC, node pools and status. Reading a cluster's workloads is the Kubernetes connector's job, this one answers what clusters exist and how they are configured.

  • List load balancers

    List the account's load balancers with each one's public IP, algorithm, forwarding rules, health check, sticky-session settings, and the droplet ids sitting behind it. Use it to find out what actually receives traffic before touching any of those droplets.

  • List billing history

    List the account's billing history, invoices, payments and other charges, each with its type, description, amount and date. Use it to answer what this account has been charged and when. Needs the billing:read scope.

Deletes or permanently changes

  • Reboot droplet

    Restart one droplet. "reboot" asks the guest operating system to restart cleanly; "power_cycle" is the equivalent of pushing the reset button, and DigitalOcean documents it as such. Both drop every live connection to the machine, and nothing replays what was in flight, which is why this is gated as destructive rather than as an ordinary write, a write grant cannot reach it. The disk is preserved either way. Returns an action; poll it with list_droplet_actions. This connector deliberately exposes only these two of the action types the endpoint accepts: rebuild and restore overwrite the disk, resize with disk changes is not reversible downward, and enable_ipv6 cannot be undone, so none of them are reachable here.

DigitalOcean in Claude Code: questions

Does Claude Code see my DigitalOcean credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in DigitalOcean?

Yes. Each of the 12 actions can be switched off for a project. Turn off the one that changes something and Claude Code can only read.

Will 12 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the DigitalOcean action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a DigitalOcean call does not run in a sandbox, so it bills nothing.

Try DigitalOcean in Claude Code

Free to start, and tool calls cost nothing on any plan.