MCP DigitalOcean Server

Created By
luc-ioa year ago
Model Context Protocol implementation with DigitalOcean integration
Overview

what is MCP DigitalOcean Server?

MCP DigitalOcean Server is a Model Context Protocol implementation that integrates with DigitalOcean for efficient server management.

how to use MCP DigitalOcean Server?

To use MCP DigitalOcean Server, clone the repository, set up your environment variables with your DigitalOcean API token, install the required dependencies, and run the server using Python.

key features of MCP DigitalOcean Server?

  • Implementation of the MCP Protocol for server management.
  • Integration with DigitalOcean for seamless server operations.
  • Built on FastAPI for high-performance HTTP server capabilities.

use cases of MCP DigitalOcean Server?

  1. Managing DigitalOcean servers using the MCP Protocol.
  2. Automating server operations and configurations.
  3. Integrating server management into larger applications using the MCP framework.

FAQ from MCP DigitalOcean Server?

  • What is the MCP Protocol?

The MCP Protocol is a framework designed for managing server contexts and operations efficiently.

  • Do I need a DigitalOcean account to use this project?

Yes, you need a DigitalOcean account to obtain an API token for integration.

  • Is there any support for this project?

You can raise issues on the GitHub repository for support.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
luc-io
Star
-
Language
-
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