MCP server · Engineering and operations

DigitalOcean MCP server

DigitalOcean in any MCP client, through Memtro: DigitalOcean does not publish this server. Memtro's DigitalOcean connector reads DigitalOcean through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

DigitalOcean cloud: droplets (servers) with status, size, region and addresses, App Platform apps with their live URL and deployment state, domains and DNS records, and the account balance, invoices and billing history. Can also power, reboot, snapshot, rename, resize, create or delete a droplet, deploy, restart or cancel a deployment of an app, create, apply or remove a tag, and add a DNS record, when you ask.

Reads

  • digitalocean_list_dropletsDigitalOcean droplets (virtual servers): name, status (new, active, off, archive), region, size, IP addresses, tags and creation date.
  • digitalocean_list_appsDigitalOcean App Platform apps: name, live URL, region, tier and the phase of the active deployment.
  • digitalocean_get_balanceThe DigitalOcean account balance: month-to-date usage and balance, and the balance as of the last invoice.
  • digitalocean_list_invoicesDigitalOcean invoices, newest first, with the current month's preview: period, amount and date.
  • digitalocean_list_billing_historyDigitalOcean billing history: invoices issued and payments made, with description, amount and date.
  • digitalocean_list_domainsDomains managed in DigitalOcean DNS: name and default TTL.
  • digitalocean_list_domain_recordsDNS records of one DigitalOcean domain: id, type, name, data, priority and TTL.

Acts, when you ask

These change something in DigitalOcean. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • digitalocean_create_tagCreate a new, empty DigitalOcean tag.
  • digitalocean_droplet_power_actionReboot, shut down, power cycle, power off or power on one DigitalOcean droplet.
  • digitalocean_snapshot_dropletTake a snapshot of one DigitalOcean droplet, with an optional name.
  • digitalocean_rename_dropletRename one DigitalOcean droplet.
  • digitalocean_resize_dropletChange one DigitalOcean droplet's size (CPU and memory) to a size slug, which changes what it costs per hour…
  • digitalocean_create_dropletCreate one DigitalOcean droplet (a virtual server) with the name, region, size, image and SSH keys given.
  • digitalocean_delete_dropletPermanently delete one DigitalOcean droplet.
  • digitalocean_deploy_appStart a new deployment of a DigitalOcean App Platform app: it pulls the latest source and, when the build succeeds, replaces the live app.
  • digitalocean_restart_appRolling restart of a DigitalOcean App Platform app, all components or only those named; requests may be briefly disrupted.
  • digitalocean_cancel_app_deploymentCancel an in-progress DigitalOcean App Platform deployment at once; the app stays on its previous live deployment.
  • digitalocean_tag_resourcesApply an existing DigitalOcean tag to the droplets, images, volumes or volume snapshots given by id.
  • digitalocean_untag_resourcesRemove a DigitalOcean tag from the droplets, images, volumes or volume snapshots given by id.
  • digitalocean_create_dns_recordAdd an A, AAAA, CNAME or MX record to a domain in DigitalOcean DNS (from digitalocean_list_domains).

Connect it

First connect DigitalOcean on Dashboard → Connections, then add Memtro to your client once. The DigitalOcean tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared DigitalOcean connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which droplets are running, and in which regions?
  • › Is the customer portal app deployed, and what is its live URL?
  • › What have we spent on DigitalOcean so far this month?
  • › Redeploy the customer portal app from its latest source
  • › Take a snapshot of the db-staging droplet before the upgrade

Questions

Is this an official DigitalOcean MCP server?
No. It is Memtro's MCP server with Memtro's DigitalOcean connector behind it: the connector reads DigitalOcean through its API with the credentials you connect on Dashboard → Connections, and DigitalOcean publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in DigitalOcean?
Only when you ask, and only what it has been granted: create a tag (does not apply it to anything); reboot, shut down, power cycle, power off or power on a droplet; take a snapshot of a droplet (snapshot storage is billed); rename a droplet; resize a droplet, which changes its price; create a droplet, which starts billed compute; permanently delete a droplet and its disk; deploy an App Platform app from its latest source; restart an App Platform app's components; cancel an in-progress App Platform deployment; apply a tag to droplets, images or volumes; remove a tag from droplets, images or volumes; add an A, AAAA, CNAME or MX record to a domain's live DNS. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time