finops-mcp
Reads an approved supplier-bills register (the invoice-intake SQLite database) in read-only mode to answer payables questions about unpaid bills due in the next N days and to include outgoing bills in the cash forecast.
Read-only access to Stripe finance data via a restricted API key: open customer invoices with aging buckets and days overdue, per-invoice detail (lines, totals, payment attempts, hosted link), recent payouts and per-payout breakdowns (sales, refunds, chargebacks, fees), open disputes with evidence deadlines, and available/pending balance per currency. Also feeds the day-by-day cash forecast with pending settlements and in-transit payouts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@finops-mcp Run a 13-day cash forecast. When do we go negative?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
finops-mcp
Ask Claude about your money, in plain English, from your real Stripe data. "Who owes us money and how late are they?" "What's in Friday's payout?" "Do we have enough cash to cover rent and payroll in the next two weeks?"
finops-mcp is a Model Context Protocol server that gives Claude (Desktop, Claude Code, or any MCP client) eight read-only finance tools over Stripe and your supplier bills. It cannot create, refund, pay or change anything.
flowchart LR
U[You ask Claude] --> C[Claude]
C <-->|MCP, read-only| F[finops-mcp]
F -->|restricted key| S[(Stripe: invoices, payouts,\nbalance, disputes)]
F -->|read-only SQLite| B[(Approved bills from\ninvoice-intake)]Tools
Tool | Answers |
| Open customer invoices, days overdue, aging buckets (current, 1-30, 31-60, 61-90, 90+), totals per currency |
| One invoice: lines, totals, payment attempts, hosted link |
| Recent payouts to the bank, arrival date and status |
| What one payout is made of: sales, refunds, chargebacks, fees, mapped to journal accounts, and a check that the lines add up to the amount that hit the bank |
| Open chargebacks with the evidence deadline and days left |
| Approved, unpaid supplier bills due in the next N days |
| Stripe available and pending, per currency |
| Day-by-day cash for one currency: lowest point, first day it goes negative, overdue invoices at risk, and the assumptions behind it |
There is also a weekly_cash_review prompt: one click in Claude Desktop runs the Monday check-in (overdue customers to chase, bills due, disputes due this week, cash low point).
Money is exact: amounts are decimals in major units, zero-decimal currencies (JPY, VND, KRW...) are handled, nothing goes through floats.
Related MCP server: Stripe MCP Server
Try it in two minutes (no Stripe account needed)
Demo mode serves a small fictional business: five open invoices (two overdue), three payouts, one chargeback, five bills.
pip install git+https://github.com/TylerNguyennn/finops-mcpAdd it to Claude Desktop (Settings → Developer → Edit Config, file claude_desktop_config.json):
{
"mcpServers": {
"finops": {
"command": "finops-mcp",
"env": { "FINOPS_DEMO": "1" }
}
}
}Or to Claude Code:
claude mcp add finops --env FINOPS_DEMO=1 -- finops-mcpThen ask: "Run a 13-day cash forecast. When do we go negative, and what would fix it?"
This is what the cash_forecast tool returns in demo mode (abridged):
opening 4,312.40 USD (Stripe available; no bank balance given)
Oct 29 +4,605.10 8,917.50 Stripe pending settles; payout po_demo_3 lands
Oct 30 -7,500.00 1,417.50 bill RENT-NOV to Riverside Property Management
Oct 31 -285.00 1,132.50 bill INV-2041 to Acme Cloud Hosting LLC
Nov 01 +980.00 2,112.50 invoice HB-1003 from Lumen Studio
Nov 04 -3,900.00 -1,787.50 bill CP-2026-11A to Crewline Contractor Payroll <- first negative
Nov 05 -1,250.00 -3,037.50 bill VA-7781 to Vector Ads Ltd <- lowest
Nov 08 +6,200.00 3,162.50 invoice HB-1004 from Atlas Fitness Group
at risk: HB-1001 Harbor Coffee Roasters 1,200.00 (10 days late), HB-1002 Pinecrest Dental 3,450.00 (20 days late)The answer is in the data: collect the two overdue invoices (4,650.00) and cash never goes below zero. The test suite checks exactly that.
Use it with your Stripe account
In Stripe, create a restricted key (Developers → API keys → Create restricted key) with Read on: Invoices, Payouts, Balance, Balance transactions, Disputes. Everything else: None.
Configure the server:
{
"mcpServers": {
"finops": {
"command": "finops-mcp",
"env": {
"STRIPE_API_KEY": "rk_live_...",
"FINOPS_BILLS_DB": "/path/to/invoice-intake/data/register.sqlite"
}
}
}
}Variable | Meaning |
| Restricted read-only key. A full |
| Optional. The register from invoice-intake: approved and exported bills that are not marked paid. Without it, |
| Payment terms for bills with no printed due date (default 30). |
| The fictional demo data above. |
Safety
Read-only by construction. The code only calls Stripe
listandretrieveendpoints; the restricted key makes that a guarantee on Stripe's side too. The bills register is opened with SQLitemode=ro. Every tool carries the MCPreadOnlyHintannotation, so clients know none of them change anything.Your data goes where your MCP client sends it. Tool results go to the Claude client you connected (for Claude Desktop, that means Anthropic's API). Nothing else leaves your machine; the server has no telemetry.
Keys live in your client config or environment, never in this repo.
How the forecast works (and what it leaves out)
Opening cash = the bank balance you pass (opening_bank_balance, default 0) + Stripe available. Stripe pending is counted pending_settles_in_days after today (default 2). Payouts already in transit land on their arrival date. Open invoices are paid on their due date; overdue ones are left out and listed as at risk unless you pass include_overdue_receivables. Approved bills are paid on their due date. New card sales, payroll and spending outside the bills register are not included. The tool returns these assumptions with every forecast so Claude repeats them.
Development
pip install -e ".[dev]"
pytest -qThe tests drive the server through a real MCP client in-process and check the numbers above, the Stripe SDK field mapping (with fake SDK objects, no network), the read-only bills register and error messages that reach the model.
finops_mcp/
sources.py Stripe and bills-register readers (+ demo versions), all amounts as Decimal
server.py the MCP tools, prompt, and env configuration
demo/ fictional data; dates are offsets from today so the demo never ages
tests/Part of a small finance-ops toolkit
stripe-payout-reconcile: split Stripe payouts into journal lines and match them to the bank statement.
invoice-intake: supplier invoices from a mailbox, read by Claude, checked, approved, exported to Xero or QuickBooks.
finops-mcp: ask Claude about receivables, payouts, disputes, bills and cash, read-only over Stripe.
Want this for your business?
I build payment and finance-ops automation: PSP integrations, webhooks, payouts, reconciliation, and Claude-based tools like this one. I can add your bank feed, Xero or QuickBooks, multi-entity or multi-currency reporting, and alerts to Slack, and deploy it for your team.
Get in touch through taewoo.me.
License
MIT
Available Tools
8 toolsbalanceARead-onlyIdempotent
Stripe balance per currency: available (can be paid out now) and pending (still settling).
Inputs: no named parameters.
cash_forecastARead-onlyIdempotent
Day-by-day cash forecast for one currency: bank balance you give + Stripe available today, Stripe pending and payouts in transit, customer invoices on their due date, approved bills on theirs. Returns each day with movement, the lowest point and the first day cash goes negative. The assumptions list in the result must be shown to the user with the numbers.
Inputs: days, currency, opening_bank_balance, pending_settles_in_days, +1 more.
disputesBRead-onlyIdempotent
Stripe disputes (chargebacks) with the evidence deadline and days left to respond.
Inputs: open_only.
invoice_detailARead-onlyIdempotent
One Stripe invoice: customer, lines, totals, payment attempts and the hosted invoice link.
Inputs: invoice_id (required).
payablesARead-onlyIdempotent
Approved supplier bills not yet paid, due within the window (overdue ones included). Needs FINOPS_BILLS_DB (an invoice-intake register) or demo mode.
Inputs: due_within_days.
payout_breakdownARead-onlyIdempotent
What one payout is made of: gross, fees and net per category (sales, refunds, chargebacks, fees), mapped to journal accounts, and whether the lines add up to the amount that hit the bank.
Inputs: payout_id (required).
payoutsBRead-onlyIdempotent
Recent Stripe payouts to the bank, newest first, with arrival date and status.
Inputs: limit.
receivablesARead-onlyIdempotent
Open customer invoices in Stripe with days overdue and an aging bucket. min_days_overdue=1 lists only overdue invoices; 0 lists everything still open.
Inputs: min_days_overdue.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct resource: receivables vs payables vs payouts vs disputes vs balance vs cash_forecast are clearly differentiated, and the two detail tools (invoice_detail, payout_breakdown) are unambiguously paired with their list counterparts via descriptions. There is no meaningful overlap that would cause misselection.
All names are lowercase noun phrases in a coherent style: plural nouns for collections (receivables, payouts, disputes, payables) and underscored compounds for detail/derived views (invoice_detail, payout_breakdown, cash_forecast). Minor deviation from a strict single convention (singular 'balance', no verb prefix) but overall predictable and readable.
Eight tools is well-scoped for a read-only FinOps reporting server, covering AR, AP, payouts, disputes, balance and forecasting without redundancy. Each tool earns its place.
Strong read-only lifecycle coverage for cash-flow reporting, including aging, payout reconciliation, disputes and a forward forecast. Minor gaps remain, such as no dedicated refunds tool or customer-level aggregation, but core financial workflows are covered.
Related MCP Connectors
Read and write Sage Intacct from Claude or ChatGPT. Write tools are flagged for approval.
Accounts receivable automation for Xero and QuickBooks Online, inside your AI assistant. Ask Claude, ChatGPT or any MCP client for a receivables summary, find customers and invoices, read the email and SMS replies your customers sent, and see what Paidnice sent or skipped. Ask why a reminder, late fee or statement did or did not go out, and update a customer's contact people straight into your ledger. Secure OAuth sign-in. One connection covers every organisation you tick, with Read or Read and Write access.
Read-only access to your own bank, card and brokerage accounts for Claude, ChatGPT and other AI agents: balances, transactions, spending, subscriptions, cashflow and investment holdings. It can never move money.
AI accounting: ask about your live AccountsOS books in plain English. Read-only tools for transactions, cash balances, invoices, bills, VAT, filing deadlines and reports across 32 countries. OAuth sign-in; free 14-day trial at accounts-os.com.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceRead-only Stripe finance, ops, and risk reporting exposed via MCP, HTTP API, and CLI. Enables querying balances, payments, customers, payouts, reconciliation, and risk alerts without mutating Stripe state.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to query Stripe data—customers, charges, subscriptions, invoices, balance, events, and more—through 17 read-oriented tools, with optional write protections and a read-only default for remote deployments.-
- AlicenseAqualityCmaintenanceEnables AI agents to query Stripe operations such as customers, recent charges, duplicate charges, and revenue summaries through read-only MCP tools.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to safely inspect Stripe billing data such as subscriptions, invoices, failed payments, and churn, with read-only access, per-tool permissions, and a tamper-evident audit log.MIT