How to integrate Digital ocean MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Digital ocean logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Digital ocean to Mastra AI using the Composio tool router. By the end, you'll have a working Digital ocean agent that can spin up a droplet for staging environment, provision a new postgresql database cluster, create a dns a record for your domain through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Digital ocean account through Composio's Digital ocean MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Digital ocean with

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Digital ocean tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Digital ocean tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Digital ocean agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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.

Supported Tools & Triggers

Tools
Create Custom ImageCreates a custom image in DigitalOcean by importing a Linux VM disk image from a publicly accessible URL.
Create Database ClusterCreates a new managed database cluster on DigitalOcean.
Create New Block Storage VolumeTool to create a new block storage volume.
Create New DomainCreates a new domain in DigitalOcean's DNS management system.
Create Domain RecordTool to create a new DNS record for a domain.
Create New DropletTool to create a new Droplet.
Create New FirewallCreates a new cloud firewall with custom inbound and outbound rules.
Create New Kubernetes ClusterCreates a new DigitalOcean Kubernetes (DOKS) cluster with managed control plane.
Create New Load BalancerTool to create a new load balancer.
Create New SSH KeyRegisters a new SSH public key with your DigitalOcean account.
Create New TagCreates a new tag in DigitalOcean for organizing and grouping resources.
Create New VPCCreates a new Virtual Private Cloud (VPC) in a specified DigitalOcean region.
Delete Block Storage VolumePermanently deletes a block storage volume by its unique ID.
Delete Database ClusterTool to delete a database cluster by UUID.
Delete DomainDeletes a domain from DigitalOcean DNS.
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 ImageDeletes a user-created custom image or snapshot from your DigitalOcean account by its numeric ID.
Delete Load BalancerTool to delete a load balancer instance by ID.
Delete SSH KeyTool to delete a public SSH key.
Delete TagDeletes a tag from your DigitalOcean account.
Delete VPCDelete a VPC (Virtual Private Cloud) by its unique identifier.
List All DatabasesTool to list all managed database clusters on your account.
List All DomainsLists all DNS domains configured in your DigitalOcean account.
List All DropletsLists all Droplets (virtual machines) in your DigitalOcean account with pagination support.
List All FirewallsList all cloud firewalls configured in 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 BalancersList all load balancers in your DigitalOcean account with pagination support.
List All SnapshotsTool to list all snapshots available on your DigitalOcean account.
List All SSH KeysLists all SSH keys associated with your DigitalOcean 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 AppsTool to list all App Platform apps in your DigitalOcean account.
List Database OptionsLists all available configuration options for DigitalOcean managed database clusters, including supported engines (PostgreSQL, MySQL, MongoDB, Valkey, Kafka, OpenSearch), versions, regions, and cluster sizes/layouts.
List Domain RecordsTool to list all DNS records for a domain.
Retrieve DomainRetrieves complete details about a specific domain including its TTL and DNS zone file configuration.
Retrieve Domain RecordTool to retrieve a specific DNS record for a domain by its record ID.
Retrieve Existing DropletRetrieve detailed information about a specific DigitalOcean Droplet by its unique numeric 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 Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK 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:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Digital ocean through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Digital ocean

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["digital_ocean"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Digital ocean MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "digital_ocean" for Digital ocean access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Digital ocean toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "digital_ocean-mastra-agent",
    instructions: "You are an AI agent with Digital ocean tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        digital_ocean: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Digital ocean toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Digital ocean and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["digital_ocean"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      digital_ocean: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "digital_ocean-mastra-agent",
    instructions: "You are an AI agent with Digital ocean tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { digital_ocean: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Digital ocean through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Digital ocean MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Digital ocean MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Digital ocean MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Digital ocean MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Digital ocean MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Digital ocean MCP with Claude Cowork

Codex logo

Codex

Use Digital ocean MCP with Codex

Cursor logo

Cursor

Use Digital ocean MCP with Cursor

OpenClaw logo

OpenClaw

Use Digital ocean MCP with OpenClaw

Hermes logo

Hermes

Use Digital ocean MCP with Hermes

CLI logo

CLI

Use Digital ocean MCP with CLI

Google ADK logo

Google ADK

Use Digital ocean MCP with Google ADK

LangChain logo

LangChain

Use Digital ocean MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Digital ocean MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Digital ocean MCP with LlamaIndex

CrewAI logo

CrewAI

Use Digital ocean MCP with CrewAI

OpenCode logo

OpenCode

Use Digital ocean MCP with OpenCode

VS Code logo

VS Code

Use Digital ocean MCP with VS Code

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 Mastra AI?

Yes, you can. Mastra AI 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.

Get started for freeGet a demo↗