Log inSubmit server
OpenClaw FinOps logo

OpenClaw FinOps

Forecasts AWS, GCP, and Azure deployment costs through a remote Streamable HTTP MCP tool.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install OpenClaw FinOps

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://integritypulse.marywomack.workers.dev/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

OpenClaw FinOps MCP server gives AI agents deterministic deployment cost forecasts for supported AWS, GCP, and Azure services. It exposes one MCP tool, `forecast_deployment_cost`, over Streamable HTTP and authenticates requests with an API key. Use it when an agent needs itemized infrastructure estimates instead of generated pricing guesses. The service also applies usage limits and can surface upgrade instructions as MCP tool errors.

Use cases

  • Forecast monthly costs for a proposed AWS deployment
  • Compare supported service estimates across AWS, GCP, and Azure
  • Give coding agents itemized infrastructure cost breakdowns
  • Track free-tier forecast operations before an upgrade

Key features

  • AWS, GCP, and Azure pricing forecasts
  • Itemized deployment cost estimates
  • Streamable HTTP MCP transport
  • API-key or bearer authentication
  • Supabase-backed usage gating
  • Stripe webhook-based tier upgrades

Tools1

What OpenClaw FinOps lets your agent do. Expand a tool for its parameters.

Verified live~298 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 41d

What it can do

From the 1 tool this server returned when we ran it.

Read-only tools · 1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

2 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 1Medium 2Low 0

Scanned 9/13/2026 via OSV.dev · https://integritypulse.marywomack.workers.dev/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit6mo agoMost recent push to the default branch.
Tools exposed1Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How OpenClaw FinOps works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about OpenClaw FinOps

OpenClaw FinOps is an MCP server that connects AI coding agents to a verified pricing matrix for AWS, GCP, and Azure. Its main tool, `forecast_deployment_cost`, estimates supported service costs from usage hours and returns line-item totals. It runs remotely over Streamable HTTP and authenticates requests with an API key.

Use the documented remote Streamable HTTP endpoint in your MCP client, or self-host it with npm and Wrangler. Self-hosting requires Supabase and Stripe secrets, followed by `npx wrangler dev` for local use or `npx wrangler deploy` for Cloudflare Workers.

Yes, OpenClaw FinOps works with Cursor through a Streamable HTTP MCP configuration. Add the documented Worker URL to `.cursor/mcp.json` and provide the `x-api-key` header with your API key.

It supports AWS, GCP, and Azure.

The server returns an MCP tool result with `isError: true` and an upgrade message after 25 free operations in a month. It does not return an HTTP 402 or 429 for this condition, so the message can be surfaced in the agent conversation.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenClaw FinOps AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/openclaw-finops?style=directory)](https://allmcps.com/mcp/openclaw-finops)
HTML Embed
<a href="https://allmcps.com/mcp/openclaw-finops"><img src="https://allmcps.com/api/badge/openclaw-finops?style=directory" alt="OpenClaw FinOps on AllMCPs" /></a>