Mizen connector for Claude

What Mizen is

Mizen is the daily operations app for restaurants: opening and closing checklists with HACCP temperature logs, staff schedule, team, shift logbook and incidents. It is used by restaurant owners, managers and their staff, mostly in France. The app and its data are in French.

The Mizen connector lets an owner or manager ask Claude about their restaurant and do everyday tasks without opening the back office. Claude acts as the signed-in person, with their current permissions and nothing more.

For example: "Where do this morning's opening checklists stand?", "Any open temperature alerts?", "Add Léa as a kitchen employee at Gambetta", "Put Karim on service Saturday from 18:00 to 23:30", "Write in the logbook that the delivery comes at 7 am tomorrow, everyone must read it", "Mark the tiramisu as sold out on Click&collect", "Enrol Nadia in the loyalty card, 06 12 34 56 78, and count her 24.50 EUR ticket", "How many points does 06 12 34 56 78 have? Redeem the free coffee for them".

Connect Claude (web, desktop, mobile)

In Claude, open Settings, then Connectors. Pick Mizen from the directory, or choose Add custom connector, name it Mizen and paste the server URL: https://app.mizen.one/api/mcp.

Click Connect. Mizen opens: sign in as usual (magic link by email). If you belong to several restaurants, pick the one to connect.

Mizen shows what Claude will be able to do and where you will be sent back (claude.ai). Click Autoriser (Allow). Mizen is now available in your conversations.

Connect Claude Code

Run: claude mcp add --transport http mizen https://app.mizen.one/api/mcp. Claude Code opens the Mizen sign-in and consent page the first time you use it.

Alternatively, create a personal token in Mizen (Mon resto, then Assistants IA, then Créer un jeton). The page shows the full command to paste. The token is shown once; keep it like a password.

Tools

Connectors are for management only (owners, general managers and managers): employees and read-only accounts cannot authorize an assistant or use a token. whoami gives the signed-in person, restaurant, sites and enabled modules; get_my_shifts their own published shifts.

Read-only: get_site (zones and appliances with temperature thresholds), get_day (today's checklists: done, late, missing lines, catch-ups), list_alerts, get_scores, list_team, get_schedule (week schedule, drafts included), get_schedule_setup, list_shift_requests, get_month_hours, list_time_off_requests, list_logbook, list_checklists and get_checklist, list_products and get_inventory, get_click_collect, list_menu and list_orders, get_loyalty, list_loyalty_members and get_loyalty_member.

Write: team (add_team_member, create_invitation), schedule (create_shift as a draft, update_shift, remove_shift, publish_week, decide_time_off, decide_shift_request, set_availability, add_time_off, positions, shift and week templates, day notes, weekly hours), logbook (post_logbook_message), alerts (resolve_alert with its corrective action), checklists and their lines, zones and appliances, inventory products and families, Click&collect (menu items, options, photos, order status, pause and settings) and the loyalty card (enrol_loyalty_member, add_loyalty_purchase, redeem_loyalty_reward, adjust_loyalty_points, update_loyalty_settings). Every tool that changes or removes something existing is marked destructive, so Claude asks for approval before each call.

publish_week works in two calls. Without a confirmation code it only returns a preview (shifts to publish, who will be emailed) and a code valid for 10 minutes. With that code it publishes, and only if the draft shifts are unchanged since the preview.

Never through Claude: ticking a checklist or sending an inventory count (proof is recorded on the shared tablet), setting a PIN, archiving a person, the document vault, the staff registry and billing.

Security and permissions

OAuth 2.1 with dynamic client registration and PKCE (S256). Access tokens last one day; refresh tokens last 90 days and are rotated on every use. Only token hashes are stored.

Every call re-reads the person's role and site. Row-level security in the database scopes every query to the restaurant. A site manager only sees their own site, and nobody can grant a role above their own.

Every change made through Claude is written to the restaurant's activity log under the person's name. Claude never has access to the employee document vault (ID, bank details, health card), the staff register or billing.

Access can be cut at any time in Mizen (Mon resto, Assistants IA, Couper) or by removing the connector in Claude. Archiving a person in Mizen ends all their access immediately.

Data and privacy

Mizen only sends Claude the data needed to answer the tool call, within the person's permissions. Mizen receives tool calls and their parameters, never conversation content. Data is hosted in France.

Privacy policy (French): https://www.mizen.one/fr/privacy/, section Assistants IA. Support: bonjour@mizen.one.