About MCP Weather & DigitalOcean
MCP Weather & DigitalOcean is an MCP server for deploying and managing static websites on DigitalOcean App Platform. Its tools cover deployment setup, app and deployment details, logs, redeployment, and deletion.
Key features
- 01Deploy static websites
- 02Retrieve app information
- 03Check deployment status
- 04List and create deployments
- 05Retrieve deployment logs
- 06Delete apps
Use cases
- 01Deploy a static site from a GitHub repository
- 02Inspect an app's deployment status
- 03Review deployment logs or trigger a redeploy
- 04Remove an app from DigitalOcean App Platform
MCP support
The server exposes DigitalOcean App Platform deployment and app-management tools to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP DigitalOcean
A Model Context Protocol (MCP) server for deploying and managing static websites on DigitalOcean App Platform.
Project Structure
src/
├── index.ts # Main entry point
├── shared/ # Shared utilities
│ └── api.ts # Shared API utilities
├── digitalocean/ # DigitalOcean MCP server
│ ├── api.ts # DigitalOcean API functions
│ ├── server.ts # DigitalOcean MCP server configuration
│ └── types.ts # DigitalOcean API types
└── template/ # Template for new MCP servers
├── api.ts # Template API functions
├── server.ts # Template MCP server configuration
└── types.ts # Template API types
tests/ # Test scripts and files
Available MCP Server
DigitalOcean Server
The DigitalOcean MCP server provides tools for deploying and managing static websites on DigitalOcean App Platform using their API.
API Token Handling
The DigitalOcean MCP server will automatically look for your API token in the following locations (in order):
- As a parameter in the tool call
- Environment variables:
DO_API_TOKENorDIGITALOCEAN_API_TOKEN - A file at
~/.dotokencontaining just the token - A
.envfile in the project root withDO_API_TOKEN=your_token - A file at
~/.config/digitalocean/tokencontaining just the token
This means you can set up your token once and not have to provide it with every command.
Tools:
-
deploy-static-site: Deploy a static website to DigitalOcean App Platform
- Required Parameters:
app_name: Name for your apprepo: GitHub repository (username/repo)
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)region: Region code (e.g., nyc, sfo) - Default: "nyc"branch: Branch to deploy - Default: "main"source_dir: Directory in repo containing source code - Default: "/"build_command: Build command (if needed)output_dir: Directory where build outputs filesdeploy_on_push: Auto-deploy on git push - Default: trueenvironment_slug: Runtime environment - Default: "html"custom_domain: Custom domain (optional)
- Required Parameters:
-
get-app-info: Get information about a DigitalOcean App Platform app
- Required Parameters:
app_id: App ID
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)
- Required Parameters:
-
get-deployment-status: Get the status of a specific deployment
- Required Parameters:
app_id: App IDdeployment_id: Deployment ID
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)
- Required Parameters:
-
list-deployments: List all deployments for an app
- Required Parameters:
app_id: App ID
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)
- Required Parameters:
-
create-deployment: Create a new deployment (redeploy an app)
- Required Parameters:
app_id: App ID
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)force_build: Force a rebuild without cache - Default: false
- Required Parameters:
-
get-deployment-logs: Get logs for a deployment
- Required Parameters:
app_id: App IDdeployment_id: Deployment ID
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)
- Required Parameters:
-
delete-app: Delete an app from DigitalOcean App Platform
- Required Parameters:
app_id: App ID
- Optional Parameters:
token: DigitalOcean API token (optional if stored in environment or config files)
- Required Parameters:
Adding a New MCP Server
To add a new MCP server:
- Copy the
templatedirectory and rename it to your server name - Update the types, API functions, and server configuration
- Add your server to the main
index.tsfile
Building and Running
# Install dependencies
npm install
# Build the project
npm run build
# Run the DigitalOcean MCP server
node build/index.js
Testing
The project includes several test scripts in the tests/ directory:
test-simple.mjs: A simple test script that sends JSON-RPC requests to the MCP servertest-api.mjs: A script that directly tests the DigitalOcean APItest-mcp.mjs: A more comprehensive test for the MCP servertest-deploy.mjs: A test script specifically for the deploy-static-site tooltoken-test.mjs: A utility script to verify that the DigitalOcean API token can be read correctly
To run a test:
# Run a test script
node tests/test-simple.mjs
Cursor Integration
To use with Cursor, add the following to your .cursor/mcp.json file:
{
"mcpServers": {
"digitalocean": {
"command": "node",
"args": [
"/path/to/your/project/build/index.js"
]
}
}
}
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.