- Home
- MCP servers
- DigitalOcean Database
DigitalOcean Database
- typescript
1
GitHub Stars
typescript
Language
4 months ago
First Indexed
3 weeks ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"oladejibidmus-digitalocean-database-mcp-server": {
"command": "node",
"args": [
"/absolute/path/to/digitalocean-database-mcp/dist/index.js"
],
"env": {
"DO_API_TOKEN": "YOUR_TOKEN"
}
}
}
}You connect Cursor AI, Claude Desktop, Windsurf, VS Code, Zed, or any MCP client to DigitalOcean managed databases using a token-based MCP server. It auto-discovers your database clusters, connects by their names, and lets you run SQL queries with SSL and pooled connections, all oriented around natural language interactions with your AI-powered IDEs.
How to use
You interact with your DigitalOcean databases through natural language in your MCP-enabled IDE. Start by setting your API token, then discover your database clusters, connect by the cluster name, and run queries or inspect schemas. You can ask to show clusters, connect to production databases, describe tables, execute queries with explanations, create new tables, and surface top results from analytics.
How to install
Prerequisites: ensure you have Node.js 18 or newer and npm installed on your system.
# Clone the MCP server repository
git clone https://github.com/oladejibidmus/DigitalOcean-Database-MCP-Server.git
cd digitalocean-database-mcp
# Install dependencies
npm install
# Build the project for production
npm run build
Additional setup and usage notes
Obtain a DigitalOcean API token with Read permissions (or Read & Write for full access) and keep it secure. You will enter this token into your MCP-enabled client to authorize auto-discovery of your database clusters.
Security considerations
SSL connections are enabled by default for all communications. Tokens are kept in memory during the session and should not be stored in plaintext. Use the minimum required permissions for tokens and validate that your IPs are allowed by your DigitalOcean setup.
Troubleshooting
If you encounter issues, verify the MCP server process is running, ensure your IDE is configured with the correct path to the MCP server, and confirm your DigitalOcean token is valid and has sufficient permissions. Restart the IDE after configuration changes.
Examples of what you can say to your MCP-enabled IDE
Show me all my database clusters. Connect to my production database. List all tables and describe the users table. Run this analytics query and explain the results. Create a new table for storing blog posts. Show me the top 10 customers by revenue.
Architecture overview
AI Assistant ⇄ MCP Server ⇄ DigitalOcean DB Clusters. The MCP server manages the connection to PostgreSQL and MySQL clusters, handling SSL, pooling, and query execution, while your AI assistant provides a natural language interface.
Guided commands and endpoints
The server supports authentication, discovery, and database operations through MCP-compatible clients. Use the provided tools in your IDE to authenticate, list clusters, connect by name, execute queries, describe tables, and disconnect when finished.
Available tools
set_api_token
Set your DigitalOcean API token to authenticate and enable discovery of database clusters.
list_database_clusters
List all your DigitalOcean database clusters available to the MCP server.
connect_by_name
Connect to a cluster by its DigitalOcean name for subsequent query operations.
execute_query
Execute SQL queries against the connected database with optional parameters.
list_tables
Show all tables in the connected database.
describe_table
Get the schema details for a specific table.
get_database_info
Retrieve database version and cluster information.
disconnect_database
Close the current database connection.