How to integrate Digital ocean MCP with Claude Code

GET STARTED FOR FREE
Framework Integration Gradient
Digital ocean Logo
Claude Code Logo
divider

Introduction

Manage your Digital ocean directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Digital ocean to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Digital ocean.

Rube connected successfully

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.

What is the Digital ocean MCP server, and what's possible with it?

The Digital ocean MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your DigitalOcean account. It provides structured and secure access to your cloud infrastructure, so your agent can perform actions like creating droplets, managing domains and DNS, provisioning databases, and organizing resources on your behalf.

  • Automated droplet provisioning: Instantly spin up new virtual machines (droplets) by specifying name, region, size, and image to quickly scale your infrastructure.
  • Database and block storage management: Have your agent create managed database clusters or persistent block storage volumes with custom configurations for seamless backend scaling.
  • Domain and DNS record automation: Simplify domain setup and DNS management by letting your agent create new domains and add or update DNS records as needed.
  • Kubernetes and firewall setup: Easily deploy Kubernetes clusters and configure firewalls by defining rules, regions, and node pools—without manual dashboard work.
  • SSH key and resource tagging: Register new SSH keys for secure access or organize your infrastructure with custom tags, making resource management effortless and consistent.

Connecting Digital ocean via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Digital ocean) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Digital ocean account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["digital_ocean"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http digital_ocean-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Digital ocean. This URL will be used to connect Claude Code to Digital ocean.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Digital ocean
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Digital ocean MCP to Claude Code

bash
claude mcp add --transport http digital_ocean-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (digital_ocean-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Digital ocean MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your digital_ocean-composio entry in the list
  • This confirms that Claude Code can now access Digital ocean tools

If everything is wired up, you should see your digital_ocean-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Digital ocean

The first time you try to use Digital ocean tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Digital ocean
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Digital ocean authorization flow
  • Return to the terminal and start using Digital ocean through Claude Code

Once authenticated, you can ask Claude Code to perform Digital ocean operations in natural language. For example:

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

Complete Code

Here's the complete code to get you started with Digital ocean and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["digital_ocean"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http digital_ocean-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Digital ocean with Claude Code using Composio's MCP server. Now you can interact with Digital ocean directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Digital ocean operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Digital ocean operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Digital ocean MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Digital ocean MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Digital ocean MCP with Claude Agent SDK

Google ADK

Google ADK

Use Digital ocean MCP with Google ADK

LangChain

LangChain

Use Digital ocean MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Digital ocean MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Digital ocean MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Digital ocean MCP with LlamaIndex

CrewAI

CrewAI

Use Digital ocean MCP with CrewAI

Codex

Codex

Use Digital ocean MCP with Codex

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 Claude Code?

Yes, you can. Claude Code 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.

Book a call↗Get started for free