Obra Cfo MCP server

Obra CFO

A local-first MCP server that makes you funding-ready. You install it in your own Claude. It reads your pitch materials on your machine and runs the investment committee on you before a real one does. Nothing is uploaded.

This is the free preview of Obra's role lineup, and it stays free and local. It is the sibling of the Obra CTO: the CTO proves your build, the CFO turns that proof into a funding case. The full playbook, the deep committee, and the templates that fix each gap live in the Build with Obra community.

The Obra founders' toolkit

Two free, local, open-source MCPs built to work as a pair:

• Obra CTO: is it built? Scores your codebase and surfaces what a technical diligence would flag. GitHub · npm
• Obra CFO (this one): is it fundable? Runs the investment committee on your pitch and turns your verified build into a funding case. GitHub · npm

Run the CTO first. The CFO reads its report as grade-A technical evidence. The method, the deep versions, and Obra in beta live in Build with Obra.

Why local-first

A tool that reads your deck, plan, and financials should not ship them somewhere. This server makes no network calls. Your materials stay where they are. You can read every line of this server before you run it, which is the point of keeping it open.

Two modes

Build. If you have no deck yet or a weak one, deck_blueprint hands your Claude the framework for a fundable deck at your stage: the slide structure with an evidence bar for each, the research to run first, and the artifacts to produce before the deck exists (business plan, pricing, go-to-market). Each piece is a paste-in prompt you give your own Claude. You build it on your machine; we give the framework, not the finished writing.

Rank. When the deck exists, prepareassessment reads your materials and hands your Claude a rigorous rubric. Your Claude separates facts from assumptions, extracts your thesis, rates each dimension with evidence and confidence, finds your weakest load-bearing assumption, and runs a six-persona investment committee. Then scorefunding_readiness turns that into a stage-calibrated dashboard.

What a dashboard looks like

# Obra CFO: funding readiness
## 74 / 100 · Promising, diligence required

| Signal | Reading |
|---|---|
| Investment score | 74 / 100 |
| Confidence in assessment | 61% |
| Venture return potential | High |
| Execution risk | Medium |
| Market risk | Medium |
| Team risk | Low |
| Technical risk | Low (from Obra CTO: 88/100, grade A) |
| Recommendation | Proceed to targeted diligence |

Under it: your facts/assumptions/opinions ledger, your weakest assumption, what must be true, the unknowns register, and the committee views. Calibrated to your stage, not a one-size score.

The Obra CTO handoff

The CFO reads the Obra CTO's report from .obra/cto-report.json if it is there. A verified, tested build is grade-A technical evidence that a deck alone can never claim, and it feeds the Technical Reviewer and your Moat slide. If the report is missing, the CFO tells you to run the CTO first, because without it your technical claims rest on assertion (grade D) and an investor's diligence will cap them exactly the same way.

Tools

Claude to work through.

• deck_blueprint returns the fundable-deck framework and the prompts to build it.
• prepare_assessment reads your materials and returns the assessment rubric for your

• scorefundingreadiness turns your Claude's structured assessment into the dashboard.

A normal run is: build the deck (blueprint) or point at your existing one, prepare the assessment, then score.

Install

Add it to your Claude MCP config (Claude Desktop or Claude Code):

Shortened. The full README is on GitHub.