Menu
Mattering Automations connector

A DigitalOcean MCP built for scheduled infrastructure work

Connect one personal access token and 55 DigitalOcean nodes join your automation canvas and your AI agents: the droplet lifecycle, block storage, DNS records, App Platform redeploys, managed database housekeeping, and snapshot rotation. The read side is free to run, billing warnings are written on the nodes that start charges, and the four destructive operations are flagged so you can gate them behind a person.

55 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the DigitalOcean MCP connector does

The DigitalOcean connector for Mattering Automations is 55 nodes across the DigitalOcean v2 REST API: droplets from create through reboot, power, resize, snapshot, and destroy, block storage volumes with attach and detach, DigitalOcean DNS with full record management, App Platform apps with deployment triggers and log access, managed database clusters with in-cluster database and user management, Spaces access keys, load balancers and cloud firewalls as read surfaces, monitoring alert policies, projects, snapshots, and tags for fleet operations.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can check the account balance, list the fleet with its IPs and sizes, point a DNS record at a new address, or trigger an App Platform redeploy and watch its logs, without anyone opening the DigitalOcean control panel.

DigitalOcean also publishes its own official MCP server, and if all you want is to chat with your DigitalOcean account from an editor or a desktop assistant, that is a good tool for the job. This integration is a different shape: the same DigitalOcean operations as nodes inside a visual workflow builder on a work platform, where they run on schedules and triggers, chain with the platform's other connectors, and land results in Mattering Productivity tasks and databases. A nightly snapshot rotation, a dynamic DNS updater, or a morning spend report is workflow work, not chat work, and that is what this connector is built for.

The safety modeling is honest about infrastructure. Of the 55 nodes, 28 read and 27 act, and four of those are flagged destructive: droplet delete, volume delete, domain delete, and snapshot delete, all permanent with no trash and no restore. Database cluster create and destroy are deliberately not nodes at all, and firewall and load balancer writes did not ship either, because a wrong firewall write can lock you out of SSH fleet-wide. Nodes that start billing say so in plain words on the node.

One connection, three surfaces

  • Visual automations. Drag DigitalOcean nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every DigitalOcean node, ready to drop on the canvas

55 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 28

DigitalOcean: Get Account

Return the authenticated DigitalOcean account: email, name, team, droplet limit, and status. Zero-parameter Safe Read, so it doubles as the credential health check: 401 means the token is wrong or revoked, 200 proves the connection.

DigitalOcean: Get Action

Fetch one action (an async operation such as a reboot, snapshot, or resize) by ID and read its status: in-progress, completed, or errored. Droplet and volume action nodes return an action ID; poll this node to know when the operation actually finished.

DigitalOcean: Get App

Fetch one App Platform app by ID: full spec (services, envs, region), live URL, and the active or in-progress deployment with its phase.

DigitalOcean: Get App Logs

Retrieve the aggregate logs of an app's active deployment. The response contains URLs, not raw log text: live_url streams current logs and historic_urls point at archived logs - fetch them with an HTTP Request node. type BUILD returns build logs of the currently served deployment.

DigitalOcean: Get Balance

Return the account's current billing balance: month-to-date usage, month-to-date balance, and outstanding account balance in USD. Useful as a spend guard before nodes that create billable infrastructure.

DigitalOcean: Get Database Cluster

Fetch one managed database cluster by UUID: engine, version, node count, region, status, database names, and connection details (host, port, user, SSL).

DigitalOcean: Get Droplet

Fetch one droplet by ID: status (new, active, off, archive), public and private IPs, size, image, region, attached volumes, and tags.

DigitalOcean: Get Firewall

Fetch one cloud firewall by UUID: full inbound and outbound rule sets, status, and the droplets and tags it protects.

DigitalOcean: Get Load Balancer

Fetch one load balancer by UUID: IP, status, algorithm, forwarding rules, health check, sticky sessions, and the droplets behind it.

DigitalOcean: List Apps

List App Platform apps with their spec, live URL, active deployment, region, and tier.

DigitalOcean: List DNS Records

List the DNS records of a managed domain, with each record's ID (needed by the update and delete nodes). Filter by fully qualified name and/or record type.

DigitalOcean: List Database Clusters

List managed database clusters (PostgreSQL, MySQL, Caching/Valkey, MongoDB, Kafka, OpenSearch) with engine, version, size, status, and connection details. Cluster create and destroy are deliberately not offered as nodes; manage cluster lifecycle in the control panel.

DigitalOcean: List Database Users

List the users of a database cluster with role and connection password. Note the response includes each user's password - treat this node's output as sensitive. Not supported on Caching/Valkey clusters.

DigitalOcean: List Databases In Cluster

List the logical databases inside a cluster. Not supported on Caching/Valkey clusters (the API returns an error there).

DigitalOcean: List Domains

List the domains managed in DigitalOcean DNS, each with its TTL and full zone file.

DigitalOcean: List Droplets

List all droplets (virtual machines) on the account with status, IPs, size, region, image, and tags. Filter by exact name or by tag. By default only non-GPU droplets are returned; set type to gpus for GPU droplets.

DigitalOcean: List Firewalls

List cloud firewalls with inbound/outbound rules and the droplets and tags each applies to.

DigitalOcean: List Images

List OS images usable for creating or rebuilding droplets: distribution images (Ubuntu, Debian, Fedora...), Marketplace application images, and the account's own snapshots and custom images (set private to true for those).

DigitalOcean: List Load Balancers

List load balancers with IP, status, forwarding rules, health check settings, and attached droplets.

DigitalOcean: List Monitoring Alerts

List the account's monitoring alert policies: metric type (CPU, memory, disk, bandwidth), threshold, window, the droplets or tags covered, and where alerts are sent (email/Slack). Requires the metrics agent (monitoring true) on the covered droplets.

DigitalOcean: List Projects

List the account's projects (the organizational folders resources live in), including which is the default.

DigitalOcean: List Regions

List all DigitalOcean datacenter regions with their slugs (nyc3, sfo3, ams3...), availability, supported features, and which droplet sizes each offers. Use the slug in create nodes.

DigitalOcean: List SSH Keys

List the SSH public keys stored on the account, with the ID and fingerprint used when embedding a key into a new droplet.

DigitalOcean: List Sizes

List all droplet size slugs with vCPUs, memory, disk, transfer allowance, hourly and monthly price, and the regions where each is available. The authoritative price check before creating or resizing a droplet.

DigitalOcean: List Snapshots

List all snapshots on the account (droplet and volume), with size, source resource, and regions. Snapshots bill monthly per GiB until deleted.

DigitalOcean: List Spaces Keys

List Spaces (S3-compatible object storage) access keys with their per-bucket permission grants. Secret keys are never included - they are only shown once at creation.

DigitalOcean: List Tags

List the account's tags with a count of resources carrying each. Tags drive fleet operations: droplet list filtering, firewall targeting, and alert policy scoping.

DigitalOcean: List Volumes

List block storage volumes with size, region, filesystem, and which droplet (if any) each is attached to. Filter by exact name and/or region.

Action nodes 27

DigitalOcean: Assign Resources To Project

Move resources into a project using their URNs (uniform resource names). Purely organizational - nothing is modified or restarted. Reversible by assigning the resources to another project.

DigitalOcean: Attach Volume

Attach a block storage volume to a droplet in the same region. A volume attaches to one droplet at a time (up to 15 volumes per droplet); pre-formatted volumes auto-mount on supported images. Reversed by DigitalOcean: Detach Volume. Poll DigitalOcean: Get Action for completion.

DigitalOcean: Create App Deployment

Trigger a new deployment of an App Platform app, pulling the latest changes from its source repository - the redeploy button as a node. Poll the returned deployment via DigitalOcean: Get App until phase is ACTIVE; App Platform keeps serving the previous deployment if the new one fails, and a rollback path exists in the vendor UI.

DigitalOcean: Create DNS Record

Create a DNS record on a managed domain. Changes go live on DigitalOcean's nameservers within seconds, propagating per TTL. Reversed by DigitalOcean: Delete DNS Record.

DigitalOcean: Create Database In Cluster

Create a new empty logical database inside an existing cluster (no extra cost - it shares the cluster's resources). Not supported on Caching/Valkey clusters. Reversible by dropping the database.

DigitalOcean: Create Database User

Create a database user in a cluster. The response includes the user's randomly generated password - capture it downstream and treat the output as sensitive. Engine options (for example PostgreSQL pg_allow_replication or MongoDB roles) go in the settings object. Not supported on Caching/Valkey clusters. Reversible by deleting the user.

DigitalOcean: Create Domain

Add a domain to DigitalOcean DNS management. This creates the DNS zone only - it does not register the domain, and the registrar must point the domain at DigitalOcean's nameservers (ns1/ns2/ns3.digitalocean.com) for records to resolve. Reversed by DigitalOcean: Delete Domain.

DigitalOcean: Create Droplet

Create a new droplet (virtual machine). BILLING STARTS IMMEDIATELY, per second with a 60-second minimum, capped at the chosen size's monthly price, and continues until the droplet is destroyed - powering off does NOT stop billing. The 202 response means the create was accepted; poll DigitalOcean: Get Droplet until status is active. Reversed by DigitalOcean: Delete Droplet.

DigitalOcean: Create SSH Key

Store a new SSH public key on the account so it can be embedded into droplets at create time. Reversed by DigitalOcean: Delete SSH Key.

DigitalOcean: Create Spaces Key

Create a Spaces access key, optionally scoped to specific buckets. The response contains the secret_key EXACTLY ONCE - it can never be retrieved again, so store it immediately and treat this node's output as highly sensitive. A fullaccess grant overrides any scoped grants in the same key. Reversible by deleting the key in the control panel or API.

DigitalOcean: Create Tag

Create a new tag (it starts attached to nothing). Tag names take letters, numbers, colons, dashes, and underscores. Reversible by deleting the tag.

DigitalOcean: Create Volume

Create a block storage volume. BILLING STARTS IMMEDIATELY at the per-GiB monthly rate and continues until the volume is deleted. Volumes can only be resized upwards later (max 16 TiB). Reversed by DigitalOcean: Delete Volume.

DigitalOcean: Delete DNS Record

Delete one DNS record from a managed domain. Whatever the record pointed at stops resolving once caches expire. Reversible by recreating the record with the same values (capture them from DigitalOcean: List DNS Records first).

DigitalOcean: Delete Domain

PERMANENTLY DELETE a domain from DigitalOcean DNS, DESTROYING ALL OF ITS DNS RECORDS at once. If the domain's nameservers point at DigitalOcean, everything under it stops resolving immediately. Export the zone (DigitalOcean: List Domains includes zone_file) before deleting.

DigitalOcean: Delete Droplet

PERMANENTLY DESTROY a droplet. The virtual machine and all data on its local disk are deleted with no trash and no restore - only separately taken snapshots or backups survive. Billing for the droplet stops. A 204 response means the destroy was accepted.

DigitalOcean: Delete SSH Key

Remove an SSH key from the account. Existing droplets keep the key in their authorized_keys; only future droplet creates are affected. Reversible by re-adding the same public key.

DigitalOcean: Delete Snapshot

PERMANENTLY DELETE a snapshot. The saved disk image is gone for good - it cannot be restored and can no longer seed new droplets or volumes. The source droplet/volume itself is not touched. Billing for the snapshot stops.

DigitalOcean: Delete Volume

PERMANENTLY DELETE a block storage volume and all data on it. There is no trash and no restore - only separately taken volume snapshots survive. Detach the volume from any droplet first. Billing for the volume stops.

DigitalOcean: Detach Volume

Detach a block storage volume from a droplet. Unmount the filesystem inside the droplet first to avoid data loss on in-flight writes. The volume and its data persist (and keep billing) after detach. Reversed by DigitalOcean: Attach Volume.

DigitalOcean: Power Off Droplet

HARD power off a droplet. Per the vendor docs this is similar to cutting the power on a physical server and could lead to complications (unflushed writes may be lost); prefer a graceful shutdown from inside the machine when possible. Note a powered-off droplet still bills. Reversed by DigitalOcean: Power On Droplet.

DigitalOcean: Power On Droplet

Power on a droplet that is currently off. Returns an action object; poll DigitalOcean: Get Action until status is completed.

DigitalOcean: Reboot Droplet

Gracefully reboot a droplet, like running the reboot command from its console. Returns an action object; poll DigitalOcean: Get Action until status is completed.

DigitalOcean: Rename SSH Key

Rename a stored SSH key. Only the display name can change; the key material itself is immutable.

DigitalOcean: Resize Droplet

Resize a droplet to a different size slug, which CHANGES ITS PRICE. The droplet must be powered off first. With disk false (the default) only CPU and RAM change and the resize is reversible; with disk true the disk grows too and the resize is PERMANENT - a disk can never be shrunk back. Poll DigitalOcean: Get Action until completed, then power on.

DigitalOcean: Snapshot Droplet

Take a full-disk snapshot of a droplet. Snapshots are stored at a low monthly per-GiB rate until deleted, and can be used as the image for new droplets. The snapshot can take several minutes; poll DigitalOcean: Get Action. Reversed by DigitalOcean: Delete Snapshot.

DigitalOcean: Tag Resources

Attach an existing tag to one or more resources. Tagging changes nothing about the resources themselves, but note that tag-scoped firewalls and alert policies start applying to newly tagged droplets immediately. Reversible by untagging (the API's untag endpoint, via an HTTP Request node if needed).

DigitalOcean: Update DNS Record

Update an existing DNS record. Only the fields filled in are changed; the classic dynamic-DNS move is updating an A record's data to a new IP. Reversible by setting the previous values back.

Connecting DigitalOcean takes one credential

DigitalOcean authenticates every v2 API request with a bearer token. Generate a personal access token in the DigitalOcean control panel at cloud.digitalocean.com under API > Tokens; tokens carry the dop_v1_ prefix and are shown exactly once at creation. Tokens can be created with full access or with custom scopes that mirror create, read, update, and delete per resource; a read-only token authenticates fine but returns 403 on every write node, so the full 55-node surface needs full access or the union of the scopes your workflows use.

1

Sign in at cloud.digitalocean.com, open API in the left navigation, and generate a new personal access token. Choose full access, or custom scopes covering the resources your workflows touch, and copy the token immediately: DigitalOcean shows it once.

2

In Mattering Automations, open Connectors, click Add Connector, choose DigitalOcean, and create a credential with the token. It is a single token field: no username, no email.

3

Click Test Connection. Mattering calls DigitalOcean's account endpoint: a 200 proves the token works, a 401 means it is wrong or revoked.

4

All 55 DigitalOcean nodes appear in the canvas palette. Run DigitalOcean: List Regions and DigitalOcean: List Sizes first: the create and resize nodes need the slugs they return, and DigitalOcean: List Sizes carries the authoritative hourly and monthly price of every droplet size.

Common uses for the DigitalOcean MCP

Snapshot rotation that cleans up its own bill

DigitalOcean: List Droplets filters the fleet by tag to the machines worth protecting, DigitalOcean: Snapshot Droplet takes a full disk snapshot of each, and DigitalOcean: Get Action polls until the snapshot completes. Then the cleanup half runs: DigitalOcean: List Snapshots returns everything stored with sizes and dates, and DigitalOcean: Delete Snapshot removes generations older than the retention window, which matters because snapshots bill by stored GiB until deleted.

Dynamic DNS and validation records

DigitalOcean: List DNS Records finds a record and its ID, DigitalOcean: Update DNS Record points an A record at a new IP within seconds of the change, and DigitalOcean: Create DNS Record with DigitalOcean: Delete DNS Record handles the create-and-remove pattern that certificate DNS validation wants. A workflow that watches a home IP, a failover target, or an ACME challenge can keep a zone current without anyone touching the control panel.

The redeploy button on a schedule or an event

DigitalOcean: Create App Deployment is App Platform's redeploy button as a node: it pulls the latest changes from the app's source repository and builds. DigitalOcean: Get App polls the deployment phase until it is ACTIVE, and DigitalOcean: Get App Logs returns the live and historic log URLs when a build needs a look. A content site that rebuilds nightly, or after an editor marks a task done in Mattering Productivity, is a three-node workflow.

A morning spend and fleet report

DigitalOcean: Get Balance returns month-to-date usage in USD, and DigitalOcean: List Droplets, DigitalOcean: List Volumes, and DigitalOcean: List Snapshots enumerate what the money is buying. A scheduled sweep can write the numbers into a Mattering database, flag droplets that have sat powered off for a month (they still bill), and open a task when usage crosses a threshold. Every node in this pattern is a free read.

Provisioning that waits for a person

DigitalOcean: List Images, DigitalOcean: List Regions, and DigitalOcean: List Sizes are the lookup tables, and DigitalOcean: Create Droplet does the provisioning, with billing starting immediately, metered per second with a 60-second minimum and capped at the size's monthly price. The natural pattern is gating the create, and especially the flagged DigitalOcean: Delete Droplet, behind an approval task in Mattering Productivity: the workflow prepares everything, a person clears the task, and only then does infrastructure change.

Database and access key housekeeping

Inside an existing managed cluster, DigitalOcean: Create Database In Cluster adds a logical database at no extra cost and DigitalOcean: Create Database User provisions credentials, with DigitalOcean: List Database Users auditing who exists. DigitalOcean: Create Spaces Key issues S3-compatible object storage keys scoped to specific buckets, returning the secret exactly once. Cluster create and destroy are deliberately not nodes: lifecycle stays in the control panel.

Example: Nightly droplet snapshots with cost cleanup

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule runs the workflow each night. There is no inbound DigitalOcean trigger in this connector, so schedules are the honest pattern.

2

DigitalOcean: List Droplets filters the fleet by tag to the droplets covered by the backup policy.

3

DigitalOcean: Snapshot Droplet takes a full disk snapshot of each one, and DigitalOcean: Get Action polls each returned action until its status is completed.

4

DigitalOcean: List Snapshots returns everything stored on the account, with sizes and creation dates.

5

DigitalOcean: Delete Snapshot removes generations older than the retention window. It is flagged destructive because a deleted snapshot is gone for good, which is exactly why this step filters strictly by age.

6

A summary lands in Mattering Productivity: what was snapshotted, what was cleaned up, and the month-to-date number from DigitalOcean: Get Balance.

DigitalOcean MCP questions, answered

What DigitalOcean operations are supported?

55 nodes on the DigitalOcean v2 REST API: 28 query nodes and 27 action nodes covering account and balance, droplets (list, get, create, delete, reboot, power on, power off, snapshot, resize), images, regions and sizes, SSH keys, block storage volumes with attach and detach, domains and DNS records, App Platform (list, get, deploy, logs), managed database clusters with in-cluster database and user management, Spaces access keys, load balancers and firewalls as reads, monitoring alert policies, projects, snapshots, and tags. Deliberately not shipped: Kubernetes, container registry, certificates, VPCs, reserved IPs, functions, database cluster create and destroy, and firewall or load balancer writes.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

How is this different from DigitalOcean's official MCP server?

DigitalOcean publishes an official MCP server, and it is the right choice when the goal is chatting with your account from an editor or desktop assistant. This integration puts DigitalOcean operations inside Mattering's visual workflow builder instead: nodes run on schedules and triggers with no assistant in the loop, chain with the platform's other connectors, and write results into Mattering tasks and databases. AI assistants get the same nodes over MCP as one surface among several, so a snapshot rotation keeps running whether or not anyone is chatting.

Can this connector destroy my infrastructure?

Four nodes can, and all four are flagged destructive: DigitalOcean: Delete Droplet, DigitalOcean: Delete Volume, DigitalOcean: Delete Domain, and DigitalOcean: Delete Snapshot. Each is permanent, with no trash and no restore, and the domain delete destroys every DNS record in the zone at once. The flags make them easy to gate behind a condition, an approval task, or a manual run. Database cluster destroy, the most destructive call on the whole API, is deliberately not a node at all, and firewall writes did not ship because a wrong rule can lock out SSH fleet-wide.

Does using this connector cost money on the DigitalOcean side?

The read side is free to run: listing droplets, regions, sizes, snapshots, and the balance creates nothing and bills nothing. The write side creates real resources, and DigitalOcean bills for resources: droplets bill per second (60-second minimum, capped at the size's monthly price) from the moment DigitalOcean: Create Droplet succeeds, volumes and snapshots bill by stored GiB until deleted, and powering a droplet off does not stop its billing. There is no permanent free tier for core infrastructure; the durable free allowance is App Platform static sites, per DigitalOcean's App Platform pricing page. DigitalOcean's trial credit for new accounts changes over time, so check digitalocean.com for the current offer.

What are DigitalOcean's API rate limits?

5,000 requests per hour and 250 requests per minute per token, per DigitalOcean's API reference. Responses carry ratelimit-limit, ratelimit-remaining, and ratelimit-reset headers, and exceeding either window returns a 429. Typical automation cadence sits far below both limits; a workflow that pages hard through large fleets should raise per_page (up to 200) rather than making more, narrower calls.

What token scopes does the connector need?

DigitalOcean personal access tokens can be created with full access or with custom scopes that mirror create, read, update, and delete per resource, such as droplet:read or domain:update. A read-only token passes the connection test and runs every query node, but returns 403 on every write node. For the full 55-node surface, create the token with full access; for a tighter workflow, grant the union of the scopes it actually uses. Scopes are fixed at creation, so widening access means creating a new token.

Why do droplet actions return before the work is done?

Because the DigitalOcean API is asynchronous for anything that takes real time. DigitalOcean: Create Droplet returns 202 when the create is accepted, not when the machine is up, so poll DigitalOcean: Get Droplet until its status is active. Reboot, power, snapshot, resize, and volume attach and detach return an action object instead; poll DigitalOcean: Get Action with its ID until the status is completed. Building the poll into the workflow is the difference between a reliable automation and one that acts on a machine that does not exist yet.

55 nodes waiting on the canvas

Put DigitalOcean to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. DigitalOcean is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products