
Battery Erp
io.github.icohangar-opsPublished by GitHub account icohangar-opsv0.1.1Updated Oct 24, 2026
Battery value-chain inventory MCP: lookup SKUs, status/reorder, bin-check, audited confirmation.
Overview
Lets an assistant look up battery-material inventory, check reorder status, and record audited bin confirmations for a battery value-chain ERP.
- What you can do
- Exposes inventory tools over stdio: lookup_inventory, get_inventory_status, get_inventory_record, list_inventory, create_bin_check_request, and record_bin_confirmation. It sits on a shared InventoryService that also backs a REST adapter, so the same inventory data can be queried from an agent or a text-line workflow. The underlying library also models BOM costs, supplier scoring, pricing, and manufacturing yield, but the MCP surface is focused on inventory lookup and bin confirmation.
- When to use it
- Use it when an assistant needs to answer questions about battery material or part stock, reorder points, or inventory records, or when a human bin-check confirmation step should be recorded from an agent workflow. It is aimed at cell manufacturers, pack integrators, procurement, and finance teams working with battery supply-chain data.
- Requirements
- Local Python process installed from the PyPI package battery-erp with the mcp extra; run as python3 -m battery_erp.mcp with PYTHONPATH set to the source tree. Needs the BATTERY_ERP_CONFIRM_TOKEN environment variable for mutating bin confirmation, and optionally BATTERY_ERP_AUDIT_LOG for the JSONL audit file. Desktop only; the README says not to call MCP from a browser and to keep REST and MCP in separate terminals.
Installation
In SourceWeft
- Open Battery Erp 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
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
35% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts