Four doors, one Intake

What does not change from one door to the next

The file is read by the same engine, lines are resolved by the same rules, and the result leaves in the same adesio.bom.canonical/v1 contract. No door ever claims to have found a part: found means the file states it. One asymmetry is deliberate — the CLI applies no operator decisions, because a figure it prints is about what the tool reads, not about what somebody confirmed.

The app

For dropping a file and looking at it.

Drag a BOM onto the home page. The report opens, you correct the column roles where the engine got them wrong, you save the reading as a named format — and the next file of that shape is recognised without a question. Lines waiting on a decision collect in the review queue, one card per part rather than per line.

It is the only door where the confirm buttons exist: a downloaded report shows them inert, because there is no longer a server to talk to.

The command line

For processing a file, or a whole folder, without opening a browser.

It produces exactly the same deliverables as the app: the self-contained report, the canonical JSON, the CSVs and the search worklist. It applies no operator decisions and reads no learned formats — what it measures is what the tool understands on its own.

npm install

# one file — report, canonical JSON, CSV, and the search worklist
npm run analyze -- my-bom.xlsx \
  -o report.html --canonical canonical.json --csv bom.csv --queries queries.csv

# a sheet by name, an encoding the file lied about, a customer profile
npm run analyze -- my-bom.xlsx --sheet "BOM" --profile analyzer/profiles/cadence-atdm.json

# a whole folder, twice: pass 1 learns a format per shape, pass 2 re-reads with it
npm run corpus-run -- --dir ./boms

The HTTP API

For calling Intake from your own system.

The table below is rendered from the routing table itself, the one openapi.json comes from. An undeclared route is therefore invisible here and unreachable there, and a declared one necessarily appears — the document cannot misdescribe what the server does.

The contract schema is served at /api/schema, the OpenAPI description at /api/openapi.json. HEAD answers like GET; a verb that does not exist on a path that does returns 405 with an Allow header, not 404.

The Claude connector

So Claude reads your BOMs, with the installation's memory.

An MCP server over stdio. Claude opens the same installation the web app uses: same learned formats, same manufacturer aliases, same catalog, same decisions. A part confirmed in the app is already settled the next time round. No tool ever returns a whole BOM — every listing is paginated, and the full line is a second call.

The tools it exposes

analyze_bom

Reads a BOM from this machine and returns its coverage, counters and report id.

list_reports

Reports this installation holds, with their file name and coverage.

get_coverage

One report's counters, named so they cannot be flattened into “resolved / unresolved”.

list_lines

A page of lines, narrowed by resolution or by why it needs review.

get_line

The full canonical record of one line: identity and its basis, candidates, value, package.

search_queries

Lines the file describes but never names, as deduplicated search queries.

lookup_worklist

The distinct parts a supplier lookup would be asked about — the figure a per-part bill is counted on.

review_queue

Every part waiting on a decision, across all reports, grouped by part.

record_decision

WRITES. Records that a part IS the one on a line, is NOT, or undoes a decision.

Declare it in your Claude client's MCP configuration:

{
  "mcpServers": {
    "adesio-intake": {
      "command": "npm",
      "args": ["run", "--silent", "mcp", "-w", "analyzer"],
      "cwd": "/path/to/bom-analyzer"
    }
  }
}