IntegrityPulse FinOps MCP Server

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

Local serverstdio

What is the IntegrityPulse FinOps MCP server?

Most cloud and infrastructure work still happens through a UI a human drives. IntegrityPulse FinOps MCP server moves it into the conversation instead. Verified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix.

The short version

IntegrityPulse FinOps is a remote MCP server that gives AI coding agents accurate, real-time cloud deployment cost forecasts. Instead of your agent guessing that "an EC2 instance costs around $50/month," it calls a tool backed by a verified pricing matrix and returns a line-item breakdown.

Getting it running

wrangler on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 12 tools. What each one is for:

  • Runtime — ** Cloudflare Workers (edge, ~0ms cold start)
  • Framework — ** Hono (lightweight, Workers-native)
  • Auth — ** API key in x-api-key or Authorization: Bearer header
  • Database — ** Supabase (PostgreSQL)
  • Payments — ** Stripe Checkout + Webhooks
  • provider — "AWS" \
  • services_to_add — Array<{ service_name, estimated_usage_hours }>
  • AWS — GCP
  • elasticache.redis.t3.micro — memorystore.redis.1gb
  • s3.standard.1tb — The s3.standard.1tb tool exposed by this server
  • Cursor — The Cursor tool exposed by this server
  • cURL — The cURL tool exposed by this server

What it needs from you

Configuration is passed through the environment: YOUR_API_KEY, SUPABASE_URL, SUPABASE_SERVICE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch IntegrityPulse FinOps.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. IntegrityPulse FinOps's toolset — Runtime, Framework, Auth and 9 more — is a fair guide to whether it matches your workflow. It is maintained by maryadawson-code; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Runtime** Cloudflare Workers (edge, ~0ms cold start)
Framework** Hono (lightweight, Workers-native)
Auth** API key in x-api-key or Authorization: Bearer header
Database** Supabase (PostgreSQL)
Payments** Stripe Checkout + Webhooks
provider"AWS" \
services_to_addArray<{ service_name, estimated_usage_hours }>
AWSGCP
elasticache.redis.t3.micromemorystore.redis.1gb
s3.standard.1tbThe s3.standard.1tb tool exposed by this server.
CursorThe Cursor tool exposed by this server.
cURLThe cURL tool exposed by this server.

How to install the IntegrityPulse FinOps MCP server

{
  "mcpServers": {
    "integritypulse": {
      "type": "streamable-http",
      "url": "https://integritypulse.marywomack.workers.dev/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
YOUR_API_KEYCredential the server authenticates with.Yes
SUPABASE_URLEndpoint or connection string the server talks to.Yes
SUPABASE_SERVICE_KEYCredential the server authenticates with.Yes
STRIPE_SECRET_KEYCredential the server authenticates with.Yes
STRIPE_WEBHOOK_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use IntegrityPulse FinOps to Runtime.
  • Use IntegrityPulse FinOps to Framework.
  • Use IntegrityPulse FinOps to Auth.

Frequently asked questions

It connects IntegrityPulse FinOps to MCP-compatible AI assistants such as Claude and Cursor, exposing 12 tools (Runtime, Framework, Auth, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with IntegrityPulse FinOps directly.