Counter lets an AI assistant you trust do the routine jobs, through WordPress’s own abilities (WordPress 6.9 and later). Connect the assistant with WordPress’s MCP Adapter plugin (or anything that uses the REST API) and log it in as a user of your site with an application password (Users → your profile → Application Passwords). It can then:
- read your menus: every dish, price, dietary word, Contains and May contain line, and what is sold out;
- read your hours: the week, each day’s services, the dated changes coming up, and whether you are open right now;
- list the table requests coming up, with the guests’ details;
- write down a table someone asked for on the phone, checked against your hours like the website’s form, marked “Added by an assistant”, and emailing nobody;
- mark a dish sold out, or back on (“the hake is off”).
- suggest starter content for your country (only with an AI service connected): the same suggestions as Appearance → Adapt starter content, saved there for you to review. It changes nothing on the site; safety items are yours to check.
It cannot publish, delete or email anything, and it can only do what the user it logs in as could do: reading and adding table requests needs an Editor or an Administrator. Ask it “what’s booked for Saturday?” or “take the sticky toffee pudding off”.
To cut it off, revoke its application password on your profile, or deactivate the MCP Adapter. Nothing in Counter talks to an AI service by itself, and neither the abilities nor the menu-line writer do anything until you connect one.