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., "@Obra CFO Assess my pitch deck for seed funding readiness"
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.
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.
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.
Related MCP server: checkyourself
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.
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.
# 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 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.
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
Claude to work through.
score_funding_readiness 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.
Add it to your Claude MCP config (Claude Desktop or Claude Code):
{
"mcpServers": {
"obra-cfo": {
"command": "npx",
"args": ["-y", "obra-cfo"]
}
}
}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.
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.
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
Apache-2.0.
Return the framework for a fundable pitch deck at your stage: the slide structure with an evidence bar for each, the research to run first (as paste-in prompts for your Claude), and the artifacts to produce before the deck exists (business plan, pricing, go-to-market). Use this when you have no deck yet or a weak one. It reads your Obra CTO report if present. Then build the deck and ask the CFO to rank it.
Inputs: path, stage, sector.
Read the founder's funding materials (deck, plan, financials, one-pager) from a local path and return their contents with a rigorous assessment rubric. YOU, the host model, then assess them (separate facts from assumptions, extract the thesis, rate each dimension with evidence and confidence, find the weakest assumption, run the six-persona committee) and call score_funding_readiness with the structured result. Reads the Obra CTO report if present so technical claims rest on verified evidence. Materials stay local.
Inputs: path, files, stage.
Turn your structured assessment (from prepare_assessment) into a stage-calibrated funding-readiness dashboard: investment score, confidence, risk register, the facts/assumptions/opinions ledger, your weakest assumption, what must be true, the unknowns, and the investment committee. Reads the Obra CTO report for technical risk.
Inputs: stage (required), thesis (required), unknowns (required), committee (required), +9 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a distinct and clear purpose: deck_blueprint for creating a slide structure, prepare_assessment for reading materials and generating an assessment rubric, and score_funding_readiness for producing a readiness dashboard. There is no overlap or ambiguity among them.
The naming uses snake_case but mixes patterns: deck_blueprint is noun_noun, while prepare_assessment and score_funding_readiness are verb_noun. This inconsistency makes the set slightly less predictable, though still readable.
Three tools is a small but appropriate number for a focused funding readiness server. They cover a sequential workflow (blueprint → prepare → score). It is slightly minimal but not under-scoped for the stated purpose.
The tools cover the assessment and scoring stages but lack a tool for actual deck building or iteration (the blueprint tool instructs the agent to build the deck externally). There are notable gaps in the lifecycle, such as updating materials or handling follow-up actions.
MCP server for VC pitch-deck scoring, thesis-fit matching, and deal-flow management.
Marketplace MCP server for live venture-capital raises and agent-mediated dealflow.
Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.
MCP server for generating rough-draft project plans from natural-language prompts.
