How to integrate Digital ocean MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Digital ocean logo
OpenCode logo
divider

How to integrate Digital ocean MCP with OpenCode

This guide explains how to connect Digital ocean MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Digital ocean with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Digital ocean with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Digital ocean

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Digital ocean Composio".
  3. Complete the authentication and authorization flow, and your Digital ocean integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Digital ocean to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Digital ocean with OpenCode

Now, in the chat, ask the agent to connect to Digital ocean or give it any Digital ocean-related task.

For example, ask it to:

  • "Spin up a droplet for staging environment"
  • "Provision a new PostgreSQL database cluster"
  • "Create a DNS A record for your domain"

It will prompt you to authenticate and authorize access to Digital ocean.

That is it. Composio tools are now available in OpenCode, and your Digital ocean account is ready to use.

Supported Tools & Triggers

Tools
Create Custom ImageTool to create a new custom image by providing a url to a linux vm image.
Create Database ClusterTool to create a new managed database cluster.
Create New Block Storage VolumeTool to create a new block storage volume.
Create New DomainTool to create a new domain.
Create Domain RecordTool to create a new dns record for a domain.
Create New DropletTool to create a new droplet.
Create New FirewallTool to create a new firewall.
Create New Kubernetes ClusterTool to create a new kubernetes cluster.
Create New SSH KeyTool to create a new ssh key.
Create New TagTool to create a new tag.
Create New VPCTool to create a new vpc.
Delete Block Storage VolumeTool to delete a block storage volume by id.
Delete Database ClusterTool to delete a database cluster by uuid.
Delete DomainTool to delete a domain by name.
Delete Domain RecordTool to delete a dns record by its record id for a domain.
Delete Existing DropletTool to delete a droplet by id.
Delete FirewallTool to delete a firewall by id.
Delete ImageTool to delete a snapshot or custom image by id.
Delete Load BalancerTool to delete a load balancer instance by id.
Delete SSH KeyTool to delete a public ssh key.
Delete TagTool to delete a tag by name.
Delete VPCTool to delete a vpc by its id.
Create New Load BalancerTool to create a new load balancer.
List Domain RecordsTool to list all dns records for a domain.
List All DatabasesTool to list all managed database clusters on your account.
List All DomainsTool to list all domains in your digitalocean account.
List All DropletsTool to list all droplets in your account.
List All FirewallsTool to list all firewalls on your digitalocean account.
List All ImagesTool to list all images available on your account.
List All Kubernetes ClustersTool to list all kubernetes clusters on your account.
List All Load BalancersTool to list all load balancer instances on your account.
List All SnapshotsTool to list all snapshots available on your digitalocean account.
List All SSH KeysTool to list all ssh keys in your account.
List All TagsTool to list all tags in your account.
List All VolumesTool to list all block storage volumes available on your account.
List All VPCsTool to list all vpcs on your account.
List Database OptionsTool to list valid database engine, version, region, and size options.
Retrieve DomainTool to retrieve details about a specific domain by its name.
Retrieve Domain RecordTool to retrieve a specific dns record for a domain by its record id.
Retrieve Existing DropletTool to show information about an individual droplet by id.
Retrieve Existing ImageTool to retrieve information about an image by id or slug.
Retrieve TagTool to retrieve an individual tag by name.
Retrieve VPCTool to retrieve details about a specific vpc by its id.
Tag ResourceTool to tag resources by name.
Untag ResourceTool to untag resources by tag name.
Update Domain RecordTool to update an existing dns record for a domain.
Update VPCTool to update information about a vpc.

Way Forward

Now that Digital ocean is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Digital ocean MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Digital ocean MCP?

With a standalone Digital ocean MCP server, the agents and LLMs can only access a fixed set of Digital ocean tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Digital ocean and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Digital ocean tools.

Can I manage the permissions and scopes for Digital ocean while using Tool Router?

Yes, absolutely. You can configure which Digital ocean scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Digital ocean data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.