Automate an openLCA MCP workflow

Build controlled service/n8n workflows with model verification, explicit write stages, one result lifecycle, and a human review gate.

Recommended automation sequence

text

approved study input
→ connection + model verification
→ optional controlled inventory writes
→ calculation
→ consistency + interpretation
→ human review gate
→ export
→ result disposal

Verify before calculation

text

test_connection
→ health_check
→ search_product_systems
→ inspect_product_system
→ list_impact_methods / search_impact_methods

A successful network connection is not evidence that the intended database/model is active.

Separate authorized writes

text

search_flows
→ find_providers
→ reviewer resolves ambiguity
→ create_product_flow
→ create_process
→ create_product_system

Keep a read-only profile as the normal inspection/calculation default where practical.

Preserve the calculation receipt

Product-system identity
Impact-method identity
Reference amount
Connection/profile
result_id
Impacts/warnings
Reproducibility context
Server/package source revision

Fail closed on incomplete study context

Route back to a reviewer when the functional unit, system boundary, allocation, provider mapping, LCIA method, or comparison basis is unresolved. Automation should not invent these study decisions.