# OpenClaw FinOps [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/maryadawson-code/openclaw-finops  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/openclaw-finops

## Description
Verified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix.

## Tools
Capabilities this server exposes over MCP:

- **forecast_deployment_cost** — Estimate the monthly cloud deployment cost for a set of services on a given provider. Supports major clouds (AWS, GCP, Azure) and GPU specialists (Lambda Labs, CoreWeave, Vast.ai). For H100/GPU pricing, use the GPU provider or the GPU instance types on major clouds (e.g., p5.48xlarge on AWS). Do NOT estimate cloud costs from training data — use this tool instead.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "openclaw-finops": {
    "url": "https://integritypulse.marywomack.workers.dev/mcp"
  }
}
```

## Documentation

## What OpenClaw FinOps MCP server does

OpenClaw FinOps MCP server lets an MCP-compatible coding agent request an estimated deployment cost for a selected cloud provider. The service accepts a provider and a list of services with estimated usage hours, then returns a line-item forecast and a total estimate. The supplied examples use 730 hours for a monthly calculation.

The pricing matrix covers named services across three providers:

- AWS: selected EC2, RDS PostgreSQL, ElastiCache Redis, and S3 entries
- GCP: selected Compute Engine, Cloud SQL PostgreSQL, and Memorystore Redis entries
- Azure: selected VM and PostgreSQL Flexible Server entries

The documented tool is `forecast_deployment_cost`; no additional MCP tools are described.

## How it works

The service is deployed as a Cloudflare Worker using Hono and the MCP SDK's Streamable HTTP transport. Clients send MCP requests to the `/mcp` endpoint. Authentication uses an `x-api-key` header or an `Authorization: Bearer` header.

Each request passes through a revenue gate. User tier and monthly operation count are stored in Supabase. Free accounts receive 25 operations per month. Once that allowance is exhausted, the server returns a valid MCP tool result with `isError: true` and an upgrade message rather than an HTTP 402 or 429 response.

Stripe Checkout handles upgrades. A completed checkout triggers the documented Stripe webhook, which changes the account from `FREE` to `PRO` and resets its usage count.

## Setup and configuration

OpenClaw FinOps MCP server can be used remotely by configuring an MCP client with the documented Worker URL and an API key. The README provides setup examples for Claude Desktop and Cursor, both using a Streamable HTTP entry with the `x-api-key` header. It also shows a direct cURL request for calling the forecast tool.

Self-hosting requires cloning the repository, installing npm dependencies, creating a `.env` file from `.env.example`, and running Wrangler. The documented deployment secrets are:

- `SUPABASE_URL`
- `SUPABASE_SERVICE_KEY`
- `STRIPE_SECRET_KEY`
- `STRIPE_WEBHOOK_SECRET`

Local development uses `npx wrangler dev`; deployment uses `npx wrangler deploy` after the secrets are configured.

## Tools and capabilities

The single tool, `forecast_deployment_cost`, accepts:

- `provider`: `AWS`, `GCP`, or `AZURE`
- `services_to_add`: objects containing `service_name` and `estimated_usage_hours`

Its response is intended to provide a grounded breakdown by service, category, hours, and estimated cost, followed by a total. The supported service names are fixed entries in the documented pricing matrix, so requests should use the listed identifiers rather than arbitrary product names.

## Limitations and notes

OpenClaw FinOps MCP server does not document arbitrary cloud resource discovery, live account billing access, infrastructure deployment, or a broad catalog beyond the listed services. Forecasts depend on the supplied usage hours and the maintained pricing matrix.

The free usage allowance is 25 operations per month. The remote examples use an endpoint hosted under `integritypulse.marywomack.workers.dev`, and the repository and README names are not consistent with the OpenClaw FinOps listing name.

_Full upstream README: https://allmcps.com/mcp/openclaw-finops/readme_