ewm-ops-mcp

A warehouse operations MCP server with the control plane production agents actually need: typed tools, shadow mode, human approval, and segregation of duties.

Not a weather demo. An LLM can list overdue warehouse tasks, inspect a blocked outbound delivery, and preview a goods issue — but it cannot post GI, because this operator is not authorized. That denial is code, not a prompt.

Cursor / Claude / any MCP client
              │ stdio
              ▼
        ewm-ops-mcp
              │
     govern() choke-point
      shadow │ live+approve │ deny
              ▼
        mock EWM store
     (swap for RFC later)

Built on the same model as lattice-mcp. The mock is the point of the portfolio piece: the protocol and the policy, not a live SAP box.

Tools

Writes accept approve: true. In EWM_MODE=shadow (default) they still never execute.

Related MCP server: foreman

Run

npm install
npm test

# MCP stdio (Claude Desktop / Cursor)
npm run mcp

# HTTP for curl
npm start
curl -s localhost:4040/tools
curl -s localhost:4040/invoke -d '{"tool":"warehouse_overview"}' -H 'content-type: application/json'

Claude Desktop snippet:

{
  "mcpServers": {
    "ewm-ops": {
      "command": "npx",
      "args": ["tsx", "src/mcp.ts"],
      "cwd": "/path/to/ewm-ops-mcp"
    }
  }
}

Try this conversation

1. “Which deliveries are at risk?”

2. “Why is 80000124 blocked?”

3. “Create picking for 80000124” → error (blocked)

4. “Confirm task 9100004501” → shadow_blocked with a planned call

5. “Post goods issue for 80000123” → denied (no GI auth)

That sequence is the product.

License

MIT © Prasanna Kumar Popuri