
Obra Cfo
com.get-obraPublished by get-obra.comv0.1.1Updated Oct 24, 2026
Local-first MCP that runs an investment committee on your pitch and scores funding readiness.
Overview
A local-first MCP server that runs a simulated investment committee on your pitch materials and scores funding readiness.
- What you can do
- Build a fundable pitch deck framework with slide structure, evidence bars and paste-in prompts for your own assistant (deck_blueprint). Read pitch materials on your machine and return an assessment rubric separating facts from assumptions, rating dimensions and running a six-persona committee (prepare_assessment). Turn the structured assessment into a stage-calibrated funding-readiness dashboard with scores, risks and a recommendation (score_funding_readiness). Optionally fold in a technical report from the sibling Obra CTO server as technical evidence.
- When to use it
- Use when preparing a fundraise and you want a pre-diligence critique of your deck, plan and financials before a real investment committee sees them. Also useful for building a deck from scratch at a given stage.
- Requirements
- Runs locally over stdio, installed via npx from the npm package obra-cfo or built from source with Node.js. No accounts, API keys or environment variables are declared. It makes no network calls.
Installation
In SourceWeft
- Open Obra Cfo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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, prepare_assessment 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 score_funding_readiness
turns that into a stage-calibrated dashboard.
What a dashboard looks like
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
deck_blueprintreturns the fundable-deck framework and the prompts to build it.prepare_assessmentreads your materials and returns the assessment rubric for your Claude to work through.score_funding_readinessturns 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):
Then ask your Claude: "Give me the Obra CFO pitch deck blueprint for seed stage," or "Assess my funding materials in ./fundraise with Obra CFO."
Prefer to run from source? Clone the repo, run npm install && npm run build, and point
the config at node /absolute/path/to/obra-cfo/dist/index.js.
What this is not
Not a deck generator, not a guarantee of a term sheet, not a replacement for your own Claude reading your materials. It is the investment committee, run on you first, from your real materials and your verified build, so you walk in prepared.
What's next
The Obra CFO is the free preview. To go further:
- The full cook: the deep authoring behind each slide, current market intelligence, the full six-persona committee, and the templates that fix each gap.
- The rest of the team: the Obra CTO for build readiness, and each new role as it ships.
- Obra itself, in beta: the AI employee that runs your back office. Members go first.
See the whole toolset and where it is going at https://get-obra.com/build
The full method and the community live in Build with Obra: https://www.skool.com/build-with-obra-5361/about
License
Apache-2.0.
Source: README.md at commit 8a9ac36
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts