MCP · local developer preview
Inspect the replenishment policy
1 read-only tool. No customer data. Runs on your computer.
Product guideWhat works today
inspect_replenishment_policy returns the local policy matrix for 9 ABC/XYZ zones, criticality adjustments, lead-time defaults and units. It takes no arguments.
It cannot read live inventory or saved decisions, change rules, approve purchases or run jobs. The answer describes your checkout, not the deployed application or an approved customer policy.
1. Prepare your checkout
You need access to the Replena repository, Bun, and an MCP client that supports local stdio servers. This local developer preview does not use a hosted endpoint or an account connection.
bun install --frozen-lockfile --ignore-scripts
command -v bun
bun --no-env-file run mcp:stdioRun these commands from your Replena checkout. Keep --no-env-file; no API keys or database credentials are needed.
2. Connect your client
Add a local stdio server named replena. Set the executable to your absolute Bun path and pass --no-env-file followed by the absolute path to lib/mcp/stdio.ts. Clients that accept mcpServers JSON can use this example; replace both paths.
{
"mcpServers": {
"replena": {
"command": "/absolute/path/to/bun",
"args": [
"--no-env-file",
"/absolute/path/to/replena/lib/mcp/stdio.ts"
]
}
}
}3. Ask one question
Use inspect_replenishment_policy to explain the AX policy, its units and its limitations.
Expect structured JSON and matching text: scope = local_code_baseline, approvalStatus = not_recorded, 9 zones, lead-time rules and limitations. Ask your client to call the tool explicitly; a fluent answer alone does not prove it ran.
If it does not connect
Check both absolute paths, install the locked dependencies, and restart the MCP connection. A terminal waiting silently is normal: the server communicates over stdin/stdout. A client that only accepts an HTTPS URL cannot connect to this local server.
From the checkout, run bun --no-env-file run test:mcp to check the server contract, or bun --no-env-file run mcp:inspect to inspect tool discovery.
What comes next
For hosted inventory and saved decisions, see the buyer MCP guide and its deployment status. This local tool remains independent and does not access customer data.