This patch follows the 0.11.0 release review. Existing MCP installations need a
workshop UUID in TENANT_ID and the accompanying database migration before the
3.0.1 server starts.
v0.11.1
September 19, 2026
Stable MCP tenant boundaries and accurate public guidance
MCP access is now pinned to one workshop throughout, webhook targets are checked more strictly, and the website describes the current product, interfaces and licensing model without retired routes or plan names.
Fixed
MCP stays inside one workshop
The server now requires TENANT_ID, rejects cross-workshop RPC arguments and validates ownership before it reads or writes relationship tables. Operator PIN actions, routing and notifications also work correctly with the service-role connection used by the server.
Fixed
Stricter webhook targets
Webhook configuration accepts HTTPS endpoints only. Dispatch rejects localhost subdomains and does not follow redirects to a different target.
Changed
Clearer fit for metal fabrication
The landing page now explains the path from ERP work order to cell queue and reported production. REST and webhook integration come first; MCP remains available for approved automation.
Changed
Docs match the running product
Current guides, examples and in-app plan labels no longer refer to removed endpoints, a retired pricing route or the former Premium name.