# DigitalOcean Kubernetes MCP server
> Manage DigitalOcean Kubernetes (DOKS) clusters and node pools from any MCP-compatible client.
- Listing: https://mcp.tc/i/digitalocean-kubernetes
- Connect: use the server's own URL `https://doks.mcp.digitalocean.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: DigitalOcean
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage:
## About
Connects an MCP client to DigitalOcean Kubernetes (DOKS) through the DigitalOcean API, so an assistant can work with your clusters and node pools. It is one of DigitalOcean's hosted MCP servers, which cover individual services such as App Platform, Droplets and Kubernetes.
Runs as a hosted streamable HTTP endpoint at doks.mcp.digitalocean.com. Users sign in with their DigitalOcean account through OAuth. A DigitalOcean API token can be sent as a Bearer token in the Authorization header instead.
## What it can do
- Manage DigitalOcean Kubernetes (DOKS) clusters
- Manage cluster node pools
- Act on your DigitalOcean account through API-backed operations
- Sign in with OAuth or a DigitalOcean API token
## Example prompts
- "List my DigitalOcean Kubernetes clusters"
- "Show the node pools in my production DOKS cluster"
- "Add a node pool to my staging Kubernetes cluster"
- "Check which Kubernetes version my cluster is running"
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http digitalocean-kubernetes https://doks.mcp.digitalocean.com/mcp
```
2. Start Claude Code, type `/mcp`, pick **digitalocean-kubernetes** and choose **Authenticate**. A browser window opens for the DigitalOcean sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Settings → Connectors** and click **Add custom connector**.
2. Name it **DigitalOcean Kubernetes** and paste this URL:
```url
https://doks.mcp.digitalocean.com/mcp
```
3. Click **Add**, then **Connect**, and sign in when DigitalOcean asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://doks.mcp.digitalocean.com/mcp` and click **Add**.
3. Click **Connect** and sign in when DigitalOcean asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.
2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.
3. Paste `https://doks.mcp.digitalocean.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to DigitalOcean to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"digitalocean-kubernetes": {
"url": "https://doks.mcp.digitalocean.com/mcp"
}
}
}
```
Cursor shows **Needs login** next to the server. Click it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"digitalocean-kubernetes","type":"http","url":"https://doks.mcp.digitalocean.com/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"digitalocean-kubernetes": {
"type": "http",
"url": "https://doks.mcp.digitalocean.com/mcp"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"digitalocean-kubernetes": {
"serverUrl": "https://doks.mcp.digitalocean.com/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add digitalocean-kubernetes --url https://doks.mcp.digitalocean.com/mcp
codex mcp login digitalocean-kubernetes
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.digitalocean-kubernetes]
url = "https://doks.mcp.digitalocean.com/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http digitalocean-kubernetes https://doks.mcp.digitalocean.com/mcp
```
Then, inside Gemini CLI, run `/mcp auth digitalocean-kubernetes` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"digitalocean-kubernetes": {
"type": "http",
"url": "https://doks.mcp.digitalocean.com/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://doks.mcp.digitalocean.com/mcp`.
## Details
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03
---
Source: https://mcp.tc/i/digitalocean-kubernetes (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report