How to integrate Digital ocean MCP with LlamaIndex

This guide walks you through connecting Digital ocean to LlamaIndex 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 LlamaIndex 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.

Digital ocean logoDigital ocean
Api KeyOauth2

DigitalOcean is a cloud platform for deploying, managing, and scaling infrastructure. Its simplicity and developer-friendly tools let you launch projects quickly and manage resources effortlessly.

48 Tools

Introduction

This guide walks you through connecting Digital ocean to LlamaIndex 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 LlamaIndex 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 your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Digital ocean
  • Connect LlamaIndex to the Digital ocean MCP server
  • Build a Digital ocean-powered agent using LlamaIndex
  • Interact with Digital ocean through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Digital ocean account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Digital ocean

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Digital ocean access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called digital ocean_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["digital_ocean"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Digital ocean actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, digital ocean)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Digital ocean tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Digital ocean
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Digital ocean tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Digital ocean
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Digital ocean, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["digital_ocean"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Digital ocean actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Digital ocean to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Digital ocean tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Digital ocean action and event your agent gets out of the box.

Create Custom Image

Creates a custom image in DigitalOcean by importing a Linux VM disk image from a publicly accessible URL.

Create Database Cluster

Creates a new managed database cluster on DigitalOcean.

Create New Block Storage Volume

Tool to create a new block storage volume.

Create New Domain

Creates a new domain in DigitalOcean's DNS management system.

Create Domain Record

Tool to create a new DNS record for a domain.

Create New Droplet

Tool to create a new Droplet.

Create New Firewall

Creates a new cloud firewall with custom inbound and outbound rules.

Create New Kubernetes Cluster

Creates a new DigitalOcean Kubernetes (DOKS) cluster with managed control plane.

Create New Load Balancer

Tool to create a new load balancer.

Create New SSH Key

Registers a new SSH public key with your DigitalOcean account.

Create New Tag

Creates a new tag in DigitalOcean for organizing and grouping resources.

Create New VPC

Creates a new Virtual Private Cloud (VPC) in a specified DigitalOcean region.

Delete Block Storage Volume

Permanently deletes a block storage volume by its unique ID.

Delete Database Cluster

Tool to delete a database cluster by UUID.

Delete Domain

Deletes a domain from DigitalOcean DNS.

Delete Domain Record

Tool to delete a DNS record by its record ID for a domain.

Delete Existing Droplet

Tool to delete a Droplet by ID.

Delete Firewall

Tool to delete a firewall by ID.

Delete Image

Deletes a user-created custom image or snapshot from your DigitalOcean account by its numeric ID.

Delete Load Balancer

Tool to delete a load balancer instance by ID.

Delete SSH Key

Tool to delete a public SSH key.

Delete Tag

Deletes a tag from your DigitalOcean account.

Delete VPC

Delete a VPC (Virtual Private Cloud) by its unique identifier.

List All Databases

Tool to list all managed database clusters on your account.

List All Domains

Lists all DNS domains configured in your DigitalOcean account.

List All Droplets

Lists all Droplets (virtual machines) in your DigitalOcean account with pagination support.

List All Firewalls

List all cloud firewalls configured in your DigitalOcean account.

List All Images

Tool to list all images available on your account.

List All Kubernetes Clusters

Tool to list all Kubernetes clusters on your account.

List All Load Balancers

List all load balancers in your DigitalOcean account with pagination support.

List All Snapshots

Tool to list all snapshots available on your DigitalOcean account.

List All SSH Keys

Lists all SSH keys associated with your DigitalOcean account.

List All Tags

Tool to list all tags in your account.

List All Volumes

Tool to list all block storage volumes available on your account.

List All VPCs

Tool to list all VPCs on your account.

List Apps

Tool to list all App Platform apps in your DigitalOcean account.

List Database Options

Lists 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 Records

Tool to list all DNS records for a domain.

Retrieve Domain

Retrieves complete details about a specific domain including its TTL and DNS zone file configuration.

Retrieve Domain Record

Tool to retrieve a specific DNS record for a domain by its record ID.

Retrieve Existing Droplet

Retrieve detailed information about a specific DigitalOcean Droplet by its unique numeric ID.

Retrieve Existing Image

Tool to retrieve information about an image by ID or slug.

Retrieve Tag

Tool to retrieve an individual tag by name.

Retrieve VPC

Tool to retrieve details about a specific VPC by its ID.

Tag Resource

Tool to tag resources by name.

Untag Resource

Tool to untag resources by tag name.

Update Domain Record

Tool to update an existing DNS record for a domain.

Update VPC

Tool to update information about a VPC.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Digital ocean.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Digital ocean tool your agent needs.Free to start.

Start building