DigitalOcean icon

CONNECT APP

Build with DigitalOcean

The developer cloud

Infrastructure & Cloud

  • OAuth

MCP

Give your agent DigitalOcean tools

Every DigitalOcean action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's DigitalOcean account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "digital_ocean",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Add SSH Key:
const result = await mcp.callTool({
  name: "digital_ocean-add-ssh-key",
  arguments: {
    name: "Name",
    publicKey: "Public key",
  },
})

API PROXY

Call the DigitalOcean API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the DigitalOcean API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.digitalocean.com/v2/account",
})

// Any allowed DigitalOcean endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run DigitalOcean actions from your backend

Connect a user's DigitalOcean account once, then run Add SSH Key on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "digital_ocean-add-ssh-key",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    digital_ocean: { authProvisionId: "apn_xxxxxxx" },
    name: "Name",
    publicKey: "Public key",
  },
})

EVENTS

DigitalOcean triggers

Event sources your backend can deploy for users and receive through a webhook.

No DigitalOcean triggers are available yet.

MULTI-APP

Use DigitalOcean with other popular apps

Most products don't stop at one integration. Pair DigitalOcean with the other apps your users rely on, and ship use cases that span both.

REFERENCE

App details

Reference metadata for the DigitalOcean connector in the Pipedream registry.

App slug
digital_ocean
Authentication
OAuth
Categories
Infrastructure & Cloud
Actions
6
Triggers
0
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed DigitalOcean OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • read
  • write