One system for the whole business.
An open-source ERP you host yourself. Recipes, stock, production, quality, people and sales share one database, with the everyday work around them. Agents connect over MCP and can do only what the person behind them can.
The daily work sits in the same system.
Projects, tasks, a wiki, meetings and time tracking sit alongside the operational records they relate to, in one system your agents can read too. Press C to create a task and ⌘K to find anything.
Agents get a person's access, or less.
Every agent signs in with a person's token. Pick a token below to see what it can and can't do.
Whose token
Scope
Owner settings
1 of 8 requests allowed for Marcus’s token
List this week's open tasks: allowed.
Allowed, and recorded against Marcus's token.
list_tasksComment on a task: refused.
Read-only token. Only GET requests get through.
create_commentLog two hours on a task: refused.
Read-only token. Only GET requests get through.
log_timeEdit a handbook page: refused.
Read-only token. Only GET requests get through.
update_documentCheck stock levels: refused.
Marcus has no access to Stock, so neither does the token.
get_stock_levelsSend a purchase order: refused.
Marcus has no access to Purchasing, so neither does the token.
send_purchase_orderApprove a recipe version: refused.
Approvals and sign-offs are never offered to tokens. A person does these in the app.
Sign off a food-safety check: refused.
Approvals and sign-offs are never offered to tokens. A person does these in the app.
How's the winter launch looking? If anything's slipping, nudge whoever owns it.
list_projects{ "query": "winter" }
Winter product launch, in progress, due 11 Jan
list_tasks{ "project": "Winter product launch", "state": "open" }
4 open, 1 in review
get_time_report{ "group_by": "task", "period": "this_week" }
8h 30m on the launch
create_comment{ "task": "Design launch announcement graphics", … }
Comment added as Ada Park
On track: four open tasks and 8½ hours logged this week. The announcement graphics have sat in review since Monday, so I've asked Priya on the task to sign them off by Friday.
- Read-only by default
- A new token can only read. Writing is a box you tick, per token.
- Limited by module
- Untick a module and its tools disappear from the agent's list.
- Always expires
- After 30, 90, 180 or 365 days; 90 unless you choose. There is no never-expires option.
- Shown once, stored as a hash
- Revoke a token from the same page you made it on.
- Rate limited
- 120 tool calls a minute per token by default, and separate read and write limits on the API.
- Some actions need a person
- Approvals, sign-offs and safety records need a signed-in person, whatever the token allows.
More than 200 tools over MCP, from list_tasks to record_ccp_readings. Works with Claude, ChatGPT, Claude Code, Codex and any client that speaks MCP. Connect an agent
Or chat inside Knotworking, on your own key.
Press ⌘ J for the assistant. Each person adds an API key for the provider they use, and it works in Knotworking with their permissions, with no agent platform to set up. How the assistant works
Turn on only what you need.
Start with the part of the business that needs it most, then add operations, people, quality or sales as you go. Turning a module off hides it and deletes nothing.
For food manufacturers.
Most of the modules are built around running a food business, from recipes and stock to quality records and sales orders. Start with the problem you have.
Open-source MRP for food manufacturers
Demand to batch schedule to purchase orders, from one set of records.Open-source ERP for food manufacturers
Operations, people, quality and sales as modules you switch on.Food lot traceability and mock recalls
Goods in to batch to despatch, with mock recalls to prove it.HACCP and food safety records
The plan, the monitoring and the corrective actions together.Recipe costing for food manufacturers
From recipe cost roll-up to actual cost per batch.ERP and MRP your AI agents can use
Over 200 MCP tools, each limited to one person's access.
Free and open source.
Run it on a machine in the office or a small cloud server, from one Compose file. There is no account with us, no per-seat bill and no hosted plan.












This has been in review since Monday and is due on the 17th. Priya, could you sign the graphics off by Friday?