@@ -32,8 +32,9 @@ Basically, it's web AE2 for your base.
 - **[Webhooks](docs/using.md#webhooks)** — finished pinned crafts and failed
   auto-crafts posted to a Discord channel or any other webhook.
 - **[AI assistants](docs/using.md#ai-assistants)** — an MCP endpoint, so
-  Claude or another AI assistant can answer questions about the base: what's
-  running low, why a craft is slow, what a craft needs.
+  Claude or another AI assistant can answer questions about the base (what's
+  running low, why a craft is slow, what a craft needs) and request crafts
+  or set stock rules for you.
 - **[Accounts](docs/server.md#user-accounts)** — per-user tokens with
   viewer, operator, and admin roles, and a
   [private](docs/server.md#private-servers) setting so only signed-in
 
@@ -819,6 +819,20 @@ deleting the user ends it too. `PUBLIC_URL`, when set, is the issuer and
 resource URL: behind a proxy the request's own host may not be what
 clients use.
 
+**The MCP write tools have no amount cap; the plan is the guard.** A fixed
+cap can't be right for every item (100k mB of a fluid is little, 100k of an
+endgame part is a lot). `request_craft` runs the same planner as the craft
+dialog and refuses to queue when ingredients are missing unless called
+again with `force`; it returns the item's name, amount, unit and stock so
+the model can't misread what it sent. The tools that change the game carry
+`destructiveHint` (clients ask the user first) and their descriptions, and
+the server's instructions, tell the model to confirm. Each runs the page
+route's own code and role check (`commands.request_cancel`,
+`stock.set_target`...). `current_crafts` gives each busy CPU's job as a
+`job_id` and `cancel_craft` passes it back as the cancel's expected output,
+so a CPU that has moved on to another job isn't cancelled. Viewers aren't
+offered operators' tools in `tools/list`.
+
 **Progress % counts steps, not time.** The server computes it
 (`gcm/progress.py`, called from `tracking.process_jobs`), not
 craft_monitor.lua. A step is one item or fluid type in the job's
 
@@ -443,13 +443,14 @@ draws each threshold as a dashed line.
 ## AI assistants
 
 The server is also an [MCP](https://modelcontextprotocol.io) server, so an AI
-assistant can read the base and answer questions about it: "what's been
-draining fastest this week?", "why is the craft on M00 slow?", "what's
-missing to make 64 of these?". Its address is your page's address with
+assistant can answer questions about the base ("what's been draining fastest
+this week?", "why is the craft on M00 slow?", "what's missing to make 64 of
+these?") and act on them ("craft 64 of those", "keep 4k of every circuit up
+to IV"). Its address is your page's address with
 `/mcp` on the end, e.g. `https://monitor.example.com/mcp`.
 
-The assistant acts as you: it signs in with your account and sees what you
-see. It can't change anything yet: every tool reads.
+The assistant acts as you: it signs in with your account, sees what you see,
+and can only change what your [role](server.md#user-accounts) can.
 
 **claude.ai, the Claude apps, or another app that connects by URL:** add a
 custom connector with the `/mcp` address. The app sends you to this server's
@@ -482,7 +483,7 @@ An app connected through the Connect page shows under its user in
 where an admin can **Disconnect** it. Revoking the token you signed in with,
 or **New token**, disconnects it too.
 
-What the assistant can look at:
+What it can look at:
 
 | Tool | What it answers |
 |---|---|
@@ -498,6 +499,28 @@ What the assistant can look at:
 | `stock_rules` | Keep-in-stock targets and your alerts |
 | `power` | Stored EU over time and its trend |
 
+| `request_status` | Whether a craft request or cancel went through, and on which CPU |
+
+What it can change:
+
+| Tool | What it does | Who |
+|---|---|---|
+| `set_stock_alert`, `remove_stock_alert` | Your own [low-stock alerts](#stock-rules) | Anyone signed in |
+| `set_stock_target`, `remove_stock_target` | The base's keep-in-stock targets | Operators, admins |
+| `request_craft` | Asks AE2 for an amount of an item, like **Craft** on the page | Operators, admins |
+| `cancel_craft` | Cancels a CPU's job, like **Cancel** on the page | Operators, admins |
+
+`request_craft` works out the crafting plan first. If ingredients are
+missing it doesn't start, and tells the assistant what's missing; it only
+starts anyway when asked to again with `force`. There's no fixed limit on the
+amount, since what's sensible depends on the item. Instead, the tools tell
+the assistant to confirm the item and amount with you, and apps such as
+Claude ask before running anything that changes the game. `cancel_craft`
+only cancels the job the assistant saw: if the CPU has started another one
+since, nothing happens. Requests and cancels show in your
+[history](server.md#user-accounts) like ones made on the page, and an
+accepted request pins its CPU for you.
+
 Answers are only as fresh as the game's last report, the same as the page's.
 
 ## Limitations
 
@@ -46,7 +46,9 @@
     "AE2 ME network, crafting CPUs and power storage, as reported by OpenComputers scripts in the game. "
     "Start with search_items to find an item's key; the other item tools take that key, never a name. "
     "Amounts are items, or mB (millibuckets, the game's litres) for fluids. Data is as fresh as the "
-    "game's last report: say when it is old."
+    "game's last report: say when it is old. request_craft, cancel_craft and the keep-in-stock target "
+    "tools change what happens in the game: say exactly what you're about to do (item, amount, CPU) "
+    "and get the user's OK before calling them."
 )
 
 
@@ -148,10 +150,9 @@ def handle(message, headers, user):
     if method == "ping":
         result = {}
     elif method == "tools/list":
-        result = {"tools": tools.listing()}
+        result = {"tools": tools.listing(user)}
         if modern:
-            # The same list for everyone, but per-user once there are
-            # tools only some roles may use.
+            # Per user: viewers aren't offered operators' tools.
             result.update({"ttlMs": 3600000, "cacheScope": "private"})
     elif method == "tools/call":
         name = params.get("name")