# How to integrate Digital ocean MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Digital ocean MCP with Vercel AI SDK v6", "toolkit": "Digital ocean", "toolkit_slug": "digital_ocean", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/digital_ocean/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/digital_ocean/framework/ai-sdk.md", "updated_at": "2026-05-12T10:08:51.977Z" } ``` ## Introduction This guide walks you through connecting Digital ocean to Vercel AI SDK v6 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 Vercel AI SDK 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 - [ChatGPT](https://composio.dev/toolkits/digital_ocean/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/digital_ocean/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/digital_ocean/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/digital_ocean/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/digital_ocean/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/digital_ocean/framework/codex) - [Cursor](https://composio.dev/toolkits/digital_ocean/framework/cursor) - [VS Code](https://composio.dev/toolkits/digital_ocean/framework/vscode) - [OpenCode](https://composio.dev/toolkits/digital_ocean/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/digital_ocean/framework/openclaw) - [Hermes](https://composio.dev/toolkits/digital_ocean/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/digital_ocean/framework/cli) - [Google ADK](https://composio.dev/toolkits/digital_ocean/framework/google-adk) - [LangChain](https://composio.dev/toolkits/digital_ocean/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/digital_ocean/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/digital_ocean/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/digital_ocean/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Digital ocean integration - Using Composio's Tool Router to dynamically load and access Digital ocean tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## 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 | Tool slug | Name | Description | |---|---|---| | `DIGITAL_OCEAN_CREATE_CUSTOM_IMAGE` | Create Custom Image | Creates a custom image in DigitalOcean by importing a Linux VM disk image from a publicly accessible URL. Use this action to upload custom OS images (Ubuntu, Debian, CentOS, Fedora, etc.) that can later be used to create Droplets. The image will be processed asynchronously and its status can be monitored via the returned image ID. | | `DIGITAL_OCEAN_CREATE_DATABASE_CLUSTER` | Create Database Cluster | Creates a new managed database cluster on DigitalOcean. Provisions a database with specified engine (PostgreSQL, MySQL, Valkey, MongoDB, Kafka, or OpenSearch), version, region, size, and node count. Returns connection credentials and cluster details. The cluster will be in 'creating' status initially and take several minutes to become fully operational. | | `DIGITAL_OCEAN_CREATE_NEW_BLOCK_STORAGE_VOLUME` | Create New Block Storage Volume | Tool to create a new block storage volume. Use when you need to provision persistent block storage after confirming the target region supports volumes. Example: "Create a 100 GiB ext4 backup volume named 'db-backup' in nyc1." | | `DIGITAL_OCEAN_CREATE_NEW_DOMAIN` | Create New Domain | Creates a new domain in DigitalOcean's DNS management system. This adds the domain to your DigitalOcean account and allows you to manage its DNS records. Use this action when you need to: - Add a domain to DigitalOcean DNS for DNS hosting and management - Set up a new domain with an optional initial A record pointing to an IP address - Transfer DNS management of an existing domain to DigitalOcean Note: The domain name must be unique within your DigitalOcean account and use a recognized top-level domain (TLD). After creation, you can add additional DNS records using the create domain record action. | | `DIGITAL_OCEAN_CREATE_NEW_DOMAIN_RECORD` | Create Domain Record | Tool to create a new DNS record for a domain. Use after confirming domain exists and record specifics. | | `DIGITAL_OCEAN_CREATE_NEW_DROPLET` | Create New Droplet | Tool to create a new Droplet. Use when you need to provision a VM with name, region, size, and image. The `image`, `region`, and `size` must be mutually compatible — the chosen `region` must be listed in the image's available regions. | | `DIGITAL_OCEAN_CREATE_NEW_FIREWALL` | Create New Firewall | Creates a new cloud firewall with custom inbound and outbound rules. Use this action to set up network security rules that control traffic to and from your Droplets. You can specify rules using IP addresses (CIDR notation), Droplet IDs, tags, Load Balancer UUIDs, or Kubernetes cluster IDs. The firewall can be applied to specific Droplets, all Droplets with certain tags, or scoped to a VPC. Requires at least one inbound rule and one outbound rule. Supports tcp, udp, and icmp protocols. | | `DIGITAL_OCEAN_CREATE_NEW_KUBERNETES_CLUSTER` | Create New Kubernetes Cluster | Creates a new DigitalOcean Kubernetes (DOKS) cluster with managed control plane. Required: cluster name, region slug, Kubernetes version slug, and at least one node pool configuration. Optional: tags, auto-upgrade settings, maintenance policy, node labels/taints, and auto-scaling. The cluster will be created in 'provisioning' state and may take several minutes to become 'running'. Query /v2/kubernetes/options endpoint to get available regions, versions, and node sizes. | | `DIGITAL_OCEAN_CREATE_NEW_LOAD_BALANCER` | Create New Load Balancer | Tool to create a new load balancer. Use after specifying region, forwarding rules, and targets. | | `DIGITAL_OCEAN_CREATE_NEW_SSH_KEY` | Create New SSH Key | Registers a new SSH public key with your DigitalOcean account. The registered key can then be automatically added to new Droplets during creation, enabling secure SSH access. The key must be provided in OpenSSH format (ssh-rsa, ssh-ed25519, etc.) and must not already exist on the account. | | `DIGITAL_OCEAN_CREATE_NEW_TAG` | Create New Tag | Creates a new tag in DigitalOcean for organizing and grouping resources. Tags can be applied to droplets, images, volumes, volume snapshots, and databases. If a tag with the same name already exists, the API returns the existing tag (idempotent operation). Tag names must be 1-255 characters containing only letters, numbers, hyphens, or underscores. | | `DIGITAL_OCEAN_CREATE_NEW_VPC` | Create New VPC | Creates a new Virtual Private Cloud (VPC) in a specified DigitalOcean region. VPCs are private networks for isolating your resources. Traffic within a VPC is free and doesn't count toward bandwidth limits. VPCs support Droplets, managed databases, load balancers, and Kubernetes clusters. The first VPC created in a region automatically becomes the default VPC for that region. | | `DIGITAL_OCEAN_DELETE_BLOCK_STORAGE_VOLUME` | Delete Block Storage Volume | Permanently deletes a block storage volume by its unique ID. Use this tool when you need to remove an existing volume. The volume must not be attached to any Droplet before deletion. This operation cannot be undone. Returns HTTP 204 No Content on success. Note: To delete by volume name instead of ID, you would need a different endpoint that accepts both name and region parameters. | | `DIGITAL_OCEAN_DELETE_DATABASE_CLUSTER` | Delete Database Cluster | Tool to delete a database cluster by UUID. Use when you have confirmed the cluster is no longer needed. Returns HTTP 204 No Content on success. | | `DIGITAL_OCEAN_DELETE_DOMAIN` | Delete Domain | Deletes a domain from DigitalOcean DNS. This action is permanent and cannot be undone. Note: If the domain is associated with a Let's Encrypt certificate, delete the certificate first and reconfigure any resources using it (e.g., load balancer SSL termination, Spaces CDN endpoints). Returns 204 No Content on successful deletion. | | `DIGITAL_OCEAN_DELETE_DOMAIN_RECORD` | Delete Domain Record | Tool to delete a DNS record by its record ID for a domain. Use when you need to remove an existing DNS record and have the domain name and record ID. Returns HTTP 204 No Content on success. | | `DIGITAL_OCEAN_DELETE_EXISTING_DROPLET` | Delete Existing Droplet | Tool to delete a Droplet by ID. Deletion is irreversible — all data is permanently lost. Confirm droplet_id with the user and verify a backup or snapshot exists before proceeding. | | `DIGITAL_OCEAN_DELETE_FIREWALL` | Delete Firewall | Tool to delete a firewall by ID. Use when you have confirmed the firewall is no longer needed. | | `DIGITAL_OCEAN_DELETE_IMAGE` | Delete Image | Deletes a user-created custom image or snapshot from your DigitalOcean account by its numeric ID. This action permanently removes the image and cannot be undone. Only custom images and snapshots you own can be deleted - attempting to delete distribution images or marketplace applications will fail with a 403 Forbidden error. Use this when cleaning up unused images that are no longer needed and have no dependent resources. | | `DIGITAL_OCEAN_DELETE_LOAD_BALANCER` | Delete Load Balancer | Tool to delete a load balancer instance by ID. Use when you need to permanently remove an existing load balancer after confirming its ID. Returns 204 No Content on success. | | `DIGITAL_OCEAN_DELETE_SSH_KEY` | Delete SSH Key | Tool to delete a public SSH key. Use when you need to remove an SSH key from your account by its ID or fingerprint after confirming its ownership. Returns 204 No Content on success. | | `DIGITAL_OCEAN_DELETE_TAG` | Delete Tag | Deletes a tag from your DigitalOcean account. When a tag is deleted, it is automatically removed from all resources that were tagged with it. This operation is idempotent - deleting a non-existent tag will also return success (204 No Content). | | `DIGITAL_OCEAN_DELETE_VPC` | Delete VPC | Delete a VPC (Virtual Private Cloud) by its unique identifier. Use this tool when you need to permanently remove a VPC from your DigitalOcean account. Deletion is irreversible — always confirm the vpc_id with the user before proceeding. **Important Restrictions:** - Cannot delete a VPC that is the default VPC for its region - Cannot delete a VPC that has member resources (droplets, databases, load balancers, etc.) — all resources must be detached or migrated first - VPC must be empty before deletion Returns an empty response (HTTP 204) on successful deletion. | | `DIGITAL_OCEAN_LIST_ALL_DATABASES` | List All Databases | Tool to list all managed database clusters on your account. Supports pagination and filtering by tag. A single request returns only one page; iterate using `page` and `per_page` to retrieve all clusters. | | `DIGITAL_OCEAN_LIST_ALL_DOMAINS` | List All Domains | Lists all DNS domains configured in your DigitalOcean account. Returns domain names, TTL values, and complete zone files. Supports pagination for large domain lists. Use this action to discover available domains, check domain configurations, or as a prerequisite for domain-specific operations like managing DNS records. No parameters are required - calling without parameters returns the first 20 domains (default page size). | | `DIGITAL_OCEAN_LIST_ALL_DROPLETS` | List All Droplets | Lists all Droplets (virtual machines) in your DigitalOcean account with pagination support. Returns detailed information including: ID, name, specs (memory, vCPUs, disk), status, networking (IP addresses), region, image, size, tags, and VPC. Supports filtering by tag and pagination for large result sets. Use this to get an overview of your infrastructure, find specific droplets, or monitor droplet status. Default page size is 20; accounts with more droplets require explicit pagination (increment `page`, up to `per_page=200`) to avoid silently incomplete results. | | `DIGITAL_OCEAN_LIST_ALL_FIREWALLS` | List All Firewalls | List all cloud firewalls configured in your DigitalOcean account. Returns comprehensive firewall details including inbound/outbound rules, associated droplets, tags, and status. Supports pagination for accounts with many firewalls. Use this to audit network security, discover existing firewall configurations, or retrieve firewall IDs for subsequent operations. | | `DIGITAL_OCEAN_LIST_ALL_IMAGES` | List All Images | Tool to list all images available on your account. Use after obtaining a valid API token to retrieve images optionally filtered by type, private visibility, or tag_name. | | `DIGITAL_OCEAN_LIST_ALL_KUBERNETES_CLUSTERS` | List All Kubernetes Clusters | Tool to list all Kubernetes clusters on your account. Use when you need to enumerate every cluster and handle pagination. | | `DIGITAL_OCEAN_LIST_ALL_LOAD_BALANCERS` | List All Load Balancers | List all load balancers in your DigitalOcean account with pagination support. Returns load balancer details including IDs, names, IP addresses, forwarding rules, health checks, sticky sessions, assigned Droplets, and region information. Use this to get an overview of all load balancers or to find specific load balancers by iterating through results. | | `DIGITAL_OCEAN_LIST_ALL_SNAPSHOTS` | List All Snapshots | Tool to list all snapshots available on your DigitalOcean account. Use when you need to fetch and optionally filter snapshots by resource type (droplet or volume) and handle pagination for inventory or backup workflows. | | `DIGITAL_OCEAN_LIST_ALL_SSH_KEYS` | List All SSH Keys | Lists all SSH keys associated with your DigitalOcean account. Returns SSH key details including ID, name, public key content, and fingerprint. Supports pagination for accounts with many SSH keys. Use this when you need to view available SSH keys or retrieve an SSH key ID for use with other operations like creating droplets. | | `DIGITAL_OCEAN_LIST_ALL_TAGS` | List All Tags | Tool to list all tags in your account. Use when you need to retrieve available tags and pagination info. A single request returns only one page of results; iterate using `page` and `per_page` to retrieve all tags. | | `DIGITAL_OCEAN_LIST_ALL_VOLUMES` | List All Volumes | Tool to list all block storage volumes available on your account. Use when you need to retrieve volumes and optionally filter by name and region. | | `DIGITAL_OCEAN_LIST_ALL_VPCS` | List All VPCs | Tool to list all VPCs on your account. Use when you need an inventory of your VPC resources. A single request returns only one page; iterate through all pages using `page` and `per_page` (max 200) to retrieve the complete set. | | `DIGITAL_OCEAN_LIST_APPS` | List Apps | Tool to list all App Platform apps in your DigitalOcean account. Use when you need to discover app IDs by name, retrieve app metadata, or enumerate all apps with pagination support. | | `DIGITAL_OCEAN_LIST_DATABASE_OPTIONS` | 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. Use this to discover valid parameter values when creating a new database cluster. | | `DIGITAL_OCEAN_LIST_DOMAIN_RECORDS` | List Domain Records | Tool to list all DNS records for a domain. Use when you need to inspect or filter a domain's DNS configuration. | | `DIGITAL_OCEAN_RETRIEVE_DOMAIN` | Retrieve Domain | Retrieves complete details about a specific domain including its TTL and DNS zone file configuration. Use this when you need to check domain settings, verify DNS configuration, or get the full zone file contents for a domain in your DigitalOcean account. | | `DIGITAL_OCEAN_RETRIEVE_DOMAIN_RECORD` | Retrieve Domain Record | Tool to retrieve a specific DNS record for a domain by its record ID. Use when you have the domain name and record ID to fetch record details. | | `DIGITAL_OCEAN_RETRIEVE_EXISTING_DROPLET` | Retrieve Existing Droplet | Retrieve detailed information about a specific DigitalOcean Droplet by its unique numeric ID. Returns comprehensive droplet details including: current status, specifications (memory, CPU, disk), networking configuration (IPv4/IPv6 addresses), image information, region, VPC, backup settings, attached volumes, and tags. Use this when you need to check a droplet's current state, configuration, or IP addresses. | | `DIGITAL_OCEAN_RETRIEVE_EXISTING_IMAGE` | Retrieve Existing Image | Tool to retrieve information about an image by ID or slug. Use when you need detailed metadata for a known image. | | `DIGITAL_OCEAN_RETRIEVE_TAG` | Retrieve Tag | Tool to retrieve an individual tag by name. Use when you need to inspect the resources grouped under a specific tag. | | `DIGITAL_OCEAN_RETRIEVE_VPC` | Retrieve VPC | Tool to retrieve details about a specific VPC by its ID. Use when you need to inspect VPC properties for configuration or auditing. | | `DIGITAL_OCEAN_TAG_RESOURCE` | Tag Resource | Tool to tag resources by name. Use when you need to assign an existing tag to one or more resources. Returns 204 No Content on success. | | `DIGITAL_OCEAN_UNTAG_RESOURCE` | Untag Resource | Tool to untag resources by tag name. Use when you need to remove an existing tag from multiple resources in a single operation. | | `DIGITAL_OCEAN_UPDATE_DOMAIN_RECORD` | Update Domain Record | Tool to update an existing DNS record for a domain. Use when you need to modify any valid attribute of a record after confirming its record ID. | | `DIGITAL_OCEAN_UPDATE_VPC` | Update VPC | Tool to update information about a VPC. Use when you need to modify the name, description, or default status of an existing VPC. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Digital ocean MCP server is an implementation of the Model Context Protocol that connects your AI agent to Digital ocean. It provides structured and secure access so your agent can perform Digital ocean operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Digital ocean tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Digital ocean-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["digital_ocean"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Digital ocean tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to digital_ocean, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Digital ocean tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript 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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["digital_ocean"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to digital_ocean, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Digital ocean agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Digital ocean MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/digital_ocean/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/digital_ocean/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/digital_ocean/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/digital_ocean/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/digital_ocean/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/digital_ocean/framework/codex) - [Cursor](https://composio.dev/toolkits/digital_ocean/framework/cursor) - [VS Code](https://composio.dev/toolkits/digital_ocean/framework/vscode) - [OpenCode](https://composio.dev/toolkits/digital_ocean/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/digital_ocean/framework/openclaw) - [Hermes](https://composio.dev/toolkits/digital_ocean/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/digital_ocean/framework/cli) - [Google ADK](https://composio.dev/toolkits/digital_ocean/framework/google-adk) - [LangChain](https://composio.dev/toolkits/digital_ocean/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/digital_ocean/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/digital_ocean/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/digital_ocean/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### 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 Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)