DigitalOcean MCP Server

Created By
digitaloceana year ago
DigitalOcean MCP Server for deploying and managing apps on App Platform
Overview

What is DigitalOcean MCP Server?

DigitalOcean MCP Server is a tool designed for deploying and managing applications on the DigitalOcean App Platform, allowing users to interact with their apps through AI assistants without needing to write code or memorize API endpoints.

How to use DigitalOcean MCP Server?

To use the DigitalOcean MCP Server, you need to set it up with a supported MCP client like Claude Desktop or Cursor. After generating a DigitalOcean Personal Access Token, you can add the server to your MCP client configuration and start managing your apps.

Key features of DigitalOcean MCP Server?

  • Deploy new apps from GitHub repositories.
  • Redeploy existing apps with the latest changes.
  • Access logs, restart components, and delete old environments.
  • Create apps based on available regions.
  • Full management of apps through voice commands or text prompts.

Use cases of DigitalOcean MCP Server?

  1. Deploying a new web application from a GitHub repository.
  2. Managing app deployments and rollbacks through voice commands.
  3. Monitoring app performance and logs directly from an AI assistant.

FAQ from DigitalOcean MCP Server?

  • What is required to use the MCP Server?
    You need Node.js, npm, a DigitalOcean Personal Access Token, and a supported MCP client.

  • Is there any installation required?
    No installation is needed; the server runs via npx with a simple configuration.

  • Can I use it with any MCP client?
    Yes, it supports multiple clients including Claude Desktop, Cursor, and Windsurf.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
digitalocean
Star
43
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago