@digitalocean/mcp 1.0.8 → 1.0.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,23 +2,32 @@
2
2
 
3
3
  MCP DigitalOcean Integration is an open-source project that provides a comprehensive interface for managing DigitalOcean resources and performing actions using the [DigitalOcean API](https://docs.digitalocean.com/reference/api/). Built on top of the [godo](https://github.com/digitalocean/godo) library and the [MCP framework](https://github.com/mark3labs/mcp-go), this project exposes a wide range of tools to simplify cloud infrastructure management.
4
4
 
5
- > DISCLAIMER: Use of MCP technology to interact with your DigitalOcean account [can come with risks](https://www.wiz.io/blog/mcp-security-research-briefing)
5
+ > **DISCLAIMER:** "Use of MCP technology to interact with your DigitalOcean account [can come with risks](https://www.wiz.io/blog/mcp-security-research-briefing)"
6
6
 
7
- ## Installation
8
-
9
- Prerequisites:
7
+ ## Prerequisites
10
8
 
11
9
  - Node.js (v18 or later)
12
10
  - NPM (v8 or later)
13
11
 
14
- #### Local Installation
12
+ You can find installation guides at [https://nodejs.org/en/download](https://nodejs.org/en/download)
15
13
 
14
+
15
+ Verify your installation:
16
16
  ```bash
17
- npx @digitalocean/mcp --services apps
17
+ node --version
18
+ npm --version
18
19
  ```
19
- ---
20
20
 
21
- #### Using with Claude Code
21
+ ## Quick Test
22
+
23
+ To verify the MCP server works correctly, you can test it directly from the command line:
24
+ ```bash
25
+ npx @digitalocean/mcp --services apps
26
+ ```
27
+
28
+ ## Installation
29
+
30
+ ### Claude Code
22
31
 
23
32
  To add the DigitalOcean MCP server to [Claude Code](https://www.anthropic.com/claude-code), run the following command in your terminal:
24
33
 
@@ -29,38 +38,53 @@ claude mcp add digitalocean-mcp \
29
38
  ```
30
39
 
31
40
  This will:
41
+ - Add the MCP server under the default (local) scope — meaning it's only available inside the current folder.
42
+ - Register it with the name `digitalocean-mcp`.
43
+ - Enable the `apps` and `databases` services.
44
+ - Pass your DigitalOcean API token securely to the server.
45
+ - Store the configuration in your global Claude config at `~/.claude.json`, scoped to the current folder.
32
46
 
33
- * Add the MCP server under the **default (local)** scope — meaning it's only available inside the current folder.
34
- * Register it with the name `digitalocean-mcp`.
35
- * Enable the `apps` and `databases` services.
36
- * Pass your DigitalOcean API token securely to the server.
37
- * Store the configuration in your global Claude config at `~/.claude.json`, scoped to the current folder.
38
-
47
+ #### Verify Installation
39
48
  To confirm it's been added:
40
-
41
49
  ```bash
42
50
  claude mcp list
43
51
  ```
44
52
 
53
+ #### Inspect Details
45
54
  To inspect details:
46
-
47
55
  ```bash
48
56
  claude mcp get digitalocean-mcp
49
57
  ```
50
58
 
59
+ #### Remove Server
51
60
  To remove it:
52
-
53
61
  ```bash
54
62
  claude mcp remove digitalocean-mcp
55
63
  ```
56
64
 
57
- ---
65
+ ### Claude Desktop
66
+
67
+ Alternatively, add the following to your claude_desktop_config.json file.
68
+
69
+ ```json
70
+ {
71
+ "mcpServers": {
72
+ "digitalocean": {
73
+ "command": "npx",
74
+ "args": ["@digitalocean/mcp", "--services apps"],
75
+ "env": {
76
+ "DIGITALOCEAN_API_TOKEN": "YOUR_API_TOKEN"
77
+ }
78
+ }
79
+ }
80
+ }
81
+ ```
82
+
83
+ ### Claude Code (User Scope)
58
84
 
59
- ### Want to use it everywhere?
60
- **Local scope** is great when you're testing or only using the server in one project.
61
- **User scope** is better if you want it available everywhere.
85
+ Local scope is great when you're testing or only using the server in one project. User scope is better if you want it available everywhere.
62
86
 
63
- If youd like to make the server available **globally** (so you dont have to re-add it in each project), you can use the `user` scope:
87
+ If you'd like to make the server available globally (so you don't have to re-add it in each project), you can use the `user` scope:
64
88
 
65
89
  ```bash
66
90
  claude mcp add -s user digitalocean-mcp-user-scope \
@@ -69,22 +93,20 @@ claude mcp add -s user digitalocean-mcp-user-scope \
69
93
  ```
70
94
 
71
95
  This will:
72
-
73
- * Make the server available in **all folders**, not just the one you’re in
74
- * Scope it to **your user account**
75
- * Store it in your global Claude config at `~/.claude.json`
96
+ - Make the server available in all folders, not just the one you're in
97
+ - Scope it to your user account
98
+ - Store it in your global Claude config at `~/.claude.json`
76
99
 
77
100
  To remove it:
78
-
79
101
  ```bash
80
102
  claude mcp remove -s user digitalocean-mcp-user-scope
81
103
  ```
82
104
 
83
- ---
105
+ ### Cursor
84
106
 
85
- #### Using Cursor IDE
107
+ [![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=digitalocean&config=eyJjb21tYW5kIjoibnB4IEBkaWdpdGFsb2NlYW4vbWNwIC0tc2VydmljZXMgYXBwcyIsImVudiI6eyJESUdJVEFMT0NFQU5fQVBJX1RPS0VOIjoiWU9VUl9BUElfVE9LRU4ifX0%3D)
86
108
 
87
- [![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](cursor://anysphere.cursor-deeplink/mcp/install?name=digitalocean&config=eyJjb21tYW5kIjoibnB4IEBkaWdpdGFsb2NlYW4vbWNwIC0tc2VydmljZXMgYXBwcyIsImVudiI6eyJESUdJVEFMT0NFQU5fQVBJX1RPS0VOIjoiWU9VUl9ET19UT0tFTiJ9fQ%3D%3D)
109
+ Add the following to your Cursor settings file located at `~/.cursor/config.json`:
88
110
 
89
111
  ```json
90
112
  {
@@ -100,29 +122,77 @@ claude mcp remove -s user digitalocean-mcp-user-scope
100
122
  }
101
123
  ```
102
124
 
103
- #### Using VSCode
125
+ #### Verify Installation in Cursor
126
+
127
+ 1. Open Cursor and open Command Pallet ( `Shift + ⌘ + P` on Mac or `Ctrl+ Shift + P` on Windows/Linux )
128
+ 2. Search for "MCP" in the command pallet search bar
129
+ 3. Select "View: Open MCP Settings"
130
+ 4. Select "Tools & Integrations" from the left sidebar
131
+ 5. You should see "digitalocean" listed under Available MCP Servers
132
+ 6. Click on "N tools enabled" (N is the number of tools currently enabled).
133
+
134
+ #### Debugging in Cursor
135
+
136
+ To check MCP server logs and debug issues:
137
+ 1. Open the Command Palette (⌘+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux)
138
+ 2. Type "Developer: Toggle Developer Tools" and press Enter
139
+ 3. Navigate to the Console tab to view MCP server logs
140
+ 4. You'll find MCP related logs as you interact with the MCP server
141
+
142
+ #### Testing the Connection
143
+
144
+ In Cursor's chat, try asking: "List all my DigitalOcean apps" - this should trigger the MCP server to fetch your apps if properly configured. If you are getting an 401 error or authentication related errors, it is likely due to misconfiguring your access token.
145
+
146
+ ### VS Code
147
+
148
+ Add the following to your VS Code MCP configuration file:
149
+
104
150
  ```json
105
151
  {
106
- "mcp": {
107
- "inputs": [],
108
- "servers": {
109
- "mcpDigitalOcean": {
110
- "command": "npx",
111
- "args": [
112
- "@digitalocean/mcp",
113
- "--services",
114
- "apps"
115
- ],
116
- "env": {
117
- "DIGITALOCEAN_API_TOKEN": "YOUR_API_TOKEN"
118
- }
119
- }
152
+ "mcp": {
153
+ "inputs": [],
154
+ "servers": {
155
+ "mcpDigitalOcean": {
156
+ "command": "npx",
157
+ "args": [
158
+ "@digitalocean/mcp",
159
+ "--services",
160
+ "apps"
161
+ ],
162
+ "env": {
163
+ "DIGITALOCEAN_API_TOKEN": "YOUR_API_TOKEN"
120
164
  }
165
+ }
121
166
  }
167
+ }
122
168
  }
123
169
  ```
124
170
 
125
- ## Configuring Tools
171
+ #### Verify Installation in VS Code
172
+
173
+ 1. Open Cursor and open Command Pallet ( `Shift + ⌘ + P` on Mac or `Ctrl+ Shift + P` on Windows/Linux )
174
+ 2. Search for "MCP" in the command pallet search bar
175
+ 3. Select "MCP: List Servers"
176
+ 4. Verify that "mcpDigitalOcean" appears in the list of configured servers
177
+
178
+ #### Viewing Available Tools
179
+
180
+ To see what tools are available from the MCP server:
181
+ 1. Open the Command Palette (⌘+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux)
182
+ 2. Select "Agent" mode in the chatbox,
183
+ 3. Click "Configure tools" on the right, and check for digitalocean related tools under `MCP Server: mcpDigitalocean`. You should be able to list available tools like `app-create`, `app-list`, `app-delete`, etc.
184
+
185
+ #### Debugging in VS Code
186
+
187
+ To troubleshoot MCP connections:
188
+ 1. Open the Command Palette (⌘+Shift+P on Mac or Ctrl+Shift+P on Windows/Linux)
189
+ 2. Type "Developer: Toggle Developer Tools" and press Enter
190
+ 3. Navigate to the Console tab to view MCP server logs
191
+ 3. Check for connection status and error messages
192
+
193
+ If you are getting an 401 error or authentication related errors, it is likely due to misconfiguring your access token.
194
+
195
+ ## Configuration
126
196
 
127
197
  To configure tools, you use the `--services` flag to specify which service you want to enable. It is highly recommended to only
128
198
  enable the services you need to reduce context size and improve accuracy. See list of supported services below.
@@ -135,36 +205,33 @@ npx @digitalocean/mcp --services apps,droplets
135
205
 
136
206
  The MCP DigitalOcean Integration supports the following services, allowing users to manage their DigitalOcean infrastructure effectively
137
207
 
138
- | **Service** | **Description** |
139
- |-----------------|--------------------------------------------------------------------------------------------------------------------|
140
- | **apps** | Manage DigitalOcean App Platform applications, including deployments and configurations. |
141
- | **droplets** | Create, manage, resize, snapshot, and monitor droplets (virtual machines) on DigitalOcean. |
142
- | **accounts** | Get information about your DigitalOcean account, billing, balance, invoices, and SSH keys. |
143
- | **networking** | Manage domains, DNS records, certificates, firewalls, reserved IPs, VPCs, and CDNs. |
144
- | **insights** | Monitors your resources, endpoints and alert you when they're slow, unavailable, or SSL certificates are expiring. |
145
- | **spaces** | DigitalOcean Spaces object storage and Spaces access keys for S3-compatible storage. |
146
- | **databases** | Provision, manage, and monitor managed database clusters (Postgres, MySQL, Redis, etc.). |
147
- | **marketplace** | Discover and manage DigitalOcean Marketplace applications. |
148
- | **doks** | Manage DigitalOcean Kubernetes clusters and node pools. | |
149
- ---
150
- ### Service Documentation
151
-
152
- Each service provides a detailed README describing all available tools, resources, arguments, and example queries.
153
- See the following files for full documentation:
154
-
155
- - [Apps Service](./internal/apps/README.md)
156
- - [Droplet Service](./internal/droplet/README.md)
157
- - [Account Service](./internal/account/README.md)
158
- - [Networking Service](./internal/networking/README.md)
159
- - [Databases Service](./internal/dbaas/README.md)
160
- - [Insights Service](./internal/insights/README.md)
161
- - [Spaces Service](./internal/spaces/README.md)
162
- - [Marketplace Service](./internal/marketplace/README.md)
163
- - [DOKS Service](./internal/doks/README.md)
164
-
165
- ---
166
-
167
- ### Example Tool Usage
208
+ | Service | Description |
209
+ |--------------|-----------------------------------------------------------------------------------------|
210
+ | apps | Manage DigitalOcean App Platform applications, including deployments and configurations. |
211
+ | droplets | Create, manage, resize, snapshot, and monitor droplets (virtual machines) on DigitalOcean. |
212
+ | accounts | Get information about your DigitalOcean account, billing, balance, invoices, and SSH keys. |
213
+ | networking | Manage domains, DNS records, certificates, firewalls, reserved IPs, VPCs, and CDNs. |
214
+ | insights | Monitors your resources, endpoints and alert you when they're slow, unavailable, or SSL certificates are expiring. |
215
+ | spaces | DigitalOcean Spaces object storage and Spaces access keys for S3-compatible storage. |
216
+ | databases | Provision, manage, and monitor managed database clusters (Postgres, MySQL, Redis, etc.). |
217
+ | marketplace | Discover and manage DigitalOcean Marketplace applications. |
218
+ | doks | Manage DigitalOcean Kubernetes clusters and node pools. |
219
+
220
+ ## Documentation
221
+
222
+ Each service provides a detailed README describing all available tools, resources, arguments, and example queries. See the following files for full documentation:
223
+
224
+ - [Apps Service](internal/apps/README.md)
225
+ - [Droplet Service](internal/droplet/README.md)
226
+ - [Account Service](internal/account/README.md)
227
+ - [Networking Service](internal/networking/README.md)
228
+ - [Databases Service](internal/dbaas/README.md)
229
+ - [Insights Service](internal/insights/README.md)
230
+ - [Spaces Service](internal/spaces/README.md)
231
+ - [Marketplace Service](internal/marketplace/README.md)
232
+ - [DOKS Service](internal/doks/README.md)
233
+
234
+ ## Example Tools
168
235
 
169
236
  - Deploy an app from a GitHub repo: `create-app-from-spec`
170
237
  - Resize a droplet: `droplet-resize`
@@ -175,19 +242,14 @@ See the following files for full documentation:
175
242
  - Create a VPC peering connection: `vpc-peering-create`
176
243
  - Delete a VPC peering connection: `vpc-peering-delete`
177
244
 
178
- ---
179
-
180
245
  ## Contributing
181
246
 
182
247
  Contributions are welcome! If you encounter any issues or have ideas for improvements, feel free to open an issue or submit a pull request.
183
248
 
184
- ### How to Contribute
185
249
  1. Fork the repository.
186
250
  2. Create a new branch for your feature or bug fix.
187
251
  3. Submit a pull request with a clear description of your changes.
188
252
 
189
- ---
190
-
191
253
  ## License
192
254
 
193
255
  This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.
Binary file
Binary file
Binary file
Binary file
Binary file
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@digitalocean/mcp",
3
- "version": "1.0.8",
3
+ "version": "1.0.10",
4
4
  "description": "DigitalOcean MCP Implementation,",
5
5
  "author": "DigitalOcean",
6
6
  "homepage": "https://github.com/digitalocean-labs/mcp-digitalocean?tab=readme-ov-file#mcp-digitalocean-integration",