MCP server for Digital Ocean Billing integration
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-digital-ocean-billing","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Digital Ocean Billing MCP Server A Model Context Protocol (MCP) server for Digital Ocean Billing integration. This server provides read-only tools for interacting with Digital Ocean's Billing API, allowing you to view account balances, billing history, and invoices. ## Features - **Account Balance**: View your current Digital Ocean account balance - **Billing History**: Access detailed billing history and transactions - **Invoices**: Retrieve and analyze your Digital Ocean invoices - **Resources**: Access raw billing data for integration with other tools - **Prompts**: Templates for common billing analysis workflows ## Installation ```bash pip install mcp-digital_ocean_billing ``` ## Configuration This MCP server requires a Digital Ocean Personal Access Token with read access to your billing information. ### Obtaining Digital Ocean API Credentials 1. Login to your Digital Ocean account at https://cloud.digitalocean.com/ 2. Navigate to API → Tokens/Keys 3. Click "Generate New Token" 4. Name your token (e.g., "MCP Billing Access") 5. Ensure "Read" scope is selected 6. Click "Generate Token" 7. Copy and securely store the generated token - it will only be shown once! ### Environment Variables Set the following environment variables: ```bash export DIGITAL_OCEAN_BILLING_API_KEY="your_personal_access_token" ``` Optionally, you can customize the API base URL (default is https://api.digitalocean.com/v2): ```bash export DIGITAL_OCEAN_BILLING_BASE_URL="https://api.digitalocean.com/v2" ``` ## Usage ### Starting the server directly ```bash mcp-digital_ocean_billing ``` ### Using with Claude Desktop Add the following to your `claude_desktop_config.json` file: ```json { "mcpServers": { "digital-ocean-billing": { "command": "uvx", "args": [ "mcp-digital_ocean_billing" ], "env": { "DIGITAL_OCEAN_BILLING_API_KEY": "your_personal_access_token" …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.