The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Obra Cto listing page.
A local-first MCP server that scores your codebase's Build Readiness. You install it in your own Claude. Your Claude reads your code on your machine and runs your tests there. Nothing is uploaded.
This is the free preview of Obra's role lineup, and it stays free and local. The CTO reads your code and tells you what an investor's technical diligence would find: real security holes, weak design decisions, and the gaps that stop a serious review. The rest of the team (the Obra CFO for funding-ready materials, and more) lives in the Build with Obra community.
Two free, local, open-source MCPs built to work as a pair:
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.
A tool that reads your code should not ship your code somewhere. Your source never
leaves your machine. This server makes exactly one kind of network call, and only
when you run the dependency check: it sends your package names and versions to the
OSV vulnerability database, never a line of your code (you can see the single call
in src/deps.ts). Everything else is local: it returns counts, presence flags, a
redacted secrets scan, and a score. You can read every line of this server before
you run it, which is the point of keeping it open.
The Obra CTO Score, out of 100, calibrated to your stage (prototype, MVP, or growth), across six dimensions:
| Dimension | Weight |
|---|---|
| Security | 25 |
| Product reality (what is actually built) | 20 |
| Robustness | 15 |
| Architecture | 15 |
| Maintainability | 15 |
| Deploy readiness | 10 |
Every finding carries an evidence grade: A verified, B multiple sources, C partial or inferred, D claim only, E speculation. The score is built from grade A and C evidence, what is true in your code, not what a deck says. When the CTO runs your tests and they pass, reliability becomes grade A. A deck-scorer can never earn that.
Point it at a real project and you get a scored report with a ranked risk register. Here is a run on a scrappy Supabase app (anonymized):
On a well-built app it scores high and credits the good engineering. It is calibrated, not a fear machine.
scan_project reads the project and returns mechanical signals.check_dependencies checks your locked dependencies against the OSV vulnerability
database. Only package names and versions leave your machine, never your code.run_tests runs your test suite (this executes code, so your Claude asks first)
and parses the pass and fail counts.prepare_code_review selects your highest-signal files (schema and policy files,
entry points, security-relevant code) and hands them to your Claude with a checklist
tuned to your stack, including a Backend-as-a-Service lens (Supabase, Firebase) and a
design red-team that critiques the architecture, not just the code.score_build_readiness produces the Obra CTO Score with a Top Risks register.A normal run is: scan, check dependencies, run tests, prepare the code review, then score.
Add it to your Claude MCP config (Claude Desktop or Claude Code):
Then ask your Claude: "Score this project's build readiness with Obra CTO."
Prefer to run from source? Clone the repo, run npm install && npm run build, and
point the config at node /absolute/path/to/obra-cto/dist/index.js.
Not a linter, not a security scanner, not a replacement for your own Claude reading the code. It is technical-diligence readiness inside funding readiness: the question an investor's CTO would ask, answered from your real code.
The Obra CTO is the free preview. To go further:
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.