Skip to content

Artificial Intelligence

DigitalOcean MCP connector

The DigitalOcean connector brings your apps, Kubernetes clusters, SSH keys, add-ons and deployment logs to Claude, ChatGPT, Cursor and any MCP client, so your team can ask about them and act on them inside their own DigitalOcean access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect DigitalOcean to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect DigitalOcean once

  1. Open Connections, choose Add connection, and pick DigitalOcean.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a DigitalOcean API key. One person generates a token in DigitalOcean and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

digitalocean
DigitalOcean
AirOps
Algolia
Botpress
Chatvolt
Cohere
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect DigitalOcean to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect DigitalOcean to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect DigitalOcean to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect DigitalOcean to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with DigitalOcean through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Check why the last deploy failed

    Ask for the latest logs of an app and get the error lines summarized in plain language, without opening the DigitalOcean control panel and scrolling.

  • Platform

    Spin up a Kubernetes cluster from a 1-click

    Pick a 1-click Kubernetes application and have it created with the settings you describe, then confirm the action completed.

  • Support

    Find out what happened to a customer's app

    Look up an app by name, read its current configuration and recent actions, and tell the customer exactly what changed and when.

  • Security

    Review and retire old SSH keys

    List every account key, spot the ones nobody recognizes, and remove them once a person has confirmed they are no longer needed.

  • Operations

    Keep add-ons and plans in order

    See which SaaS add-ons are attached to your account, change a plan when usage grows, and drop the ones that are no longer used.

  • Product

    Ship a small config change to an app

    Update an environment variable or scaling setting on an app after a decision in standup, and check the resulting action went through.

Try asking

  • “List every DigitalOcean account key and who created it.”
  • “Show DigitalOcean actions from the last 24 hours.”
  • “Which 1-click apps run on our Kubernetes clusters?”

See all 684 DigitalOcean tools below

AI tools

DigitalOcean tools for your AI agents

684 tools are ready to call through Elaichi's MCP endpoint the moment you connect DigitalOcean, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting DigitalOcean gets you

6 screens from the product, each doing one job for your DigitalOcean account.

The agent

Ask about DigitalOcean accounts in plain language.

Starter prompts return answers from live account keys, actions and apps.

  • account keys
  • actions
  • apps
  • kubernetes clusters

Ask Elaichi to work across your apps.

List every DigitalOcean account key and who created it.

Show DigitalOcean actions from the last 24 hours.

Which 1-click apps run on our Kubernetes clusters?

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect DigitalOcean over OAuth from any MCP client, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

684 DigitalOcean tools are ready to call.

Account keys, actions, 1-click apps and Kubernetes clusters, with no custom code.

  • List all DigitalOcean 1 clicks
  • Create a DigitalOcean 1 clicks kubernete
  • List all DigitalOcean accounts
  • List all DigitalOcean account keys
ElaichiTools
Tool Action Description
List all DigitalOcean 1 clicks List List all available 1-Click applications in DigitalOcean. Returns an array of applications, each including its slug and type. Optionally filter results to a specific application type using the type parameter; currently supported types are kubernetes and droplet.
Create a DigitalOcean 1 clicks kubernete Create Install one or more Kubernetes 1-Click applications on a DigitalOcean cluster. Returns: message confirming successful addon installation. Required: addon_slugs, cluster_uuid.
List all DigitalOcean accounts List Get the DigitalOcean account associated with the authenticated credentials. Returns the account's uuid, email, email_verified, status, status_message, droplet_limit, floating_ip_limit, and volume_limit. No required parameters.
List all DigitalOcean account keys List List all SSH keys in your DigitalOcean account. Returns a collection of SSH key objects each containing id, fingerprint, public_key, and name.
Create a DigitalOcean account key Create Add a new SSH public key to your DigitalOcean account. Returns the created SSH key including its id, fingerprint, public_key, and name. Required: name, public_key.

Toolboxes

Every team gets its own DigitalOcean toolbox.

Curate toolboxes so platform, security and data teams each see their own scope.

  • Platform engineering
  • SRE
  • Security
  • Data
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

DigitalOcean · Kubernetes clusters and 1-click apps

DigitalOcean starter 18 Mar 4, 2026

SRE toolbox

DigitalOcean · actions and account status

9 Mar 2, 2026

Security toolbox

DigitalOcean · account keys and access

24 Feb 27, 2026

Data toolbox

DigitalOcean · metadata and add-ons

DigitalOcean starter 6 Feb 19, 2026

Product engineering toolbox

DigitalOcean · apps and deployments

31 Jan 30, 2026

Finance operations toolbox

DigitalOcean · accounts and SaaS add-ons

12 Jan 22, 2026

Shared connections

Teammates use DigitalOcean without seeing a token.

The connections table shows who connected each account and how widely it is shared.

  • Production
  • Staging
  • Platform
  • Security
ElaichiConnections
Connection Scope Status Access
DI

DigitalOcean (Production)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
DI

DigitalOcean (Staging)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
DI

DigitalOcean (Platform)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
DI

DigitalOcean (Security)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
DI

DigitalOcean (Data)

Connected by Clara Nowak

Personal • Active Not shared
DI

DigitalOcean (Billing)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every DigitalOcean call is written down.

When, who, what happened, type and resource, in an append,only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

DigitalOcean Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

DigitalOcean Account keys Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

DigitalOcean Account keys List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule runs six DigitalOcean steps.

Fetch actions, group them, draft a digest, get approval, post back to DigitalOcean.

DigitalOcean digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch account keys

    DigitalOcean

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    DigitalOcean

    Queued

Collections and dashboards

DigitalOcean health arrives before anyone asks.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

DigitalOcean health

Refreshed 4 minutes ago · every 15 minutes · from the account keys collection

Live

Account keys

1,284 ↓ 12%

Actions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Account keys created

Last 14 days

By team

Share of activity

Production 34%

Staging 27%

Platform 21%

Security 18%

FAQ

Frequently asked questions

How do I connect DigitalOcean to Claude?

Connect DigitalOcean in Elaichi first: paste a personal access token from your DigitalOcean account, since DigitalOcean connects with an API key rather than a sign-in screen. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself when Claude asks, and your DigitalOcean apps, clusters and keys are available in the conversation.

Does DigitalOcean work with ChatGPT and Cursor as well as Claude?

Yes. Once DigitalOcean is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect DigitalOcean once and every client you use picks it up.

What can an AI agent actually do with my DigitalOcean data?

With DigitalOcean connected, an agent can list your apps and read their deployment logs, create or update an app, create a Kubernetes cluster from a 1-click, and manage SSH keys and SaaS add-ons on the account. It can also look up recent actions to tell you what changed and whether it finished. Because DigitalOcean exposes several hundred actions, short concrete asks such as "show the last logs for the billing app" get better results than long paragraphs.

Does connecting DigitalOcean give the AI access to my whole account?

No. Every call to DigitalOcean runs with the access of the person who signed in, so an agent sees the apps, clusters and keys that person's DigitalOcean token can already reach and nothing more. Elaichi can narrow that further with restrictions per action, but it can never widen it beyond what DigitalOcean itself allows that person.

Can my team share one DigitalOcean connection?

Yes. One person connects DigitalOcean in Elaichi and shares the connection with a team, and nobody else ever handles the DigitalOcean API key. Each teammate still signs in to Elaichi as themselves, so every change to an app or cluster in the audit log carries the name of the person who made it.

Can I stop an agent from deleting or changing things in DigitalOcean?

Yes. In Elaichi you can block individual DigitalOcean actions, for example deleting an app, removing an SSH key or changing an add-on plan, while leaving read-only ones open. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, accidental or otherwise, can reach it.

What happens to a DigitalOcean connection when someone leaves?

Offboarding a person in Elaichi ends their access to DigitalOcean through every connected client at once. If they had shared a DigitalOcean connection with a team, it keeps working for everyone else. When you want DigitalOcean gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Put DigitalOcean in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.