Can Claude Create a Restaurant Menu? Yes — Here's the 2-Minute Setup
The Duckhub team builds AI-powered QR menu and online ordering software used by cafes, bars, and restaurants. We write practical guides based on what we see working across thousands of published menus.
Yes, Claude can create a restaurant menu, and not just as text in a chat. Connected to a menu platform through a custom connector, Claude builds the real thing: categories, dishes with prices, photos, translations, and a published QR menu guests can scan. The connector setup takes about two minutes and works on Claude’s free plan.
TL;DR
- Claude drafts menu content out of the box; connected via MCP, it creates and publishes the live menu itself.
- Setup on claude.ai: Settings → Connectors → add
https://mcp.duck-hub.com/mcp→ sign in. The free plan includes one custom connector. - Claude Code and Cursor connect to the same endpoint with an API key, for owners who live in the terminal.
- A read-only key lets Claude analyze your menu without being able to change anything.
- Review prices and allergens before saying “publish”; nothing goes live without that step.
What can Claude do for a restaurant menu?
Claude handles both halves of menu work: the writing and, once connected, the doing. On the writing side it structures a dish list into categories, writes specific ingredient-first descriptions, translates the menu, and reads a photo or PDF of your existing menu. On the doing side, a connected Claude creates those items inside your menu platform account and publishes the result.
The connection runs on MCP (Model Context Protocol), the open standard Anthropic, Claude’s maker, released in November 2024. Duck Hub MCP allows ChatGPT, Claude and other AI assistants to create a complete restaurant menu directly inside Duck Hub, and Claude was the first assistant the standard was built for, so the fit is native: Claude sees the platform as 39 typed tools covering products, images, translations, promotions, publishing, and orders.
How do you connect Claude to a menu platform?
On claude.ai, the connection is a custom connector: Settings → Connectors → Add custom connector, paste https://mcp.duck-hub.com/mcp, and click Connect. Claude opens the Duckhub sign-in (Google or email), you pick which venue it may manage, and you approve a short consent screen. No API key, nothing to install.
Two facts worth knowing before you start:
- It works on the free plan. Anthropic’s custom connectors are available on every Claude plan, and the free tier includes one custom connector slot, which is exactly enough for this.
- The connection is venue-bound. Claude only sees and edits the venue you approved. You can disconnect any time from Duckhub → Integrations → Connected apps, and it takes effect on the very next request.
The full walkthrough with screenshots of each consent step is in the OAuth connection guide.
How does Claude actually build the menu?
You hand Claude your menu in whatever form it exists, and ask. A photo of the chalkboard, last year’s PDF, a plain typed list: Claude extracts categories, dishes, and prices from any of them and creates the real items through the platform’s tools, with the platform validating every call.
A typical first session:
- Upload the source. “Here’s a photo of our current menu. Build it in Duckhub: every category, dish, and price, plus a one-line description for each dish.”
- Let it work. Claude calls the menu tools one by one; invalid data (a malformed price, an over-limit item) is rejected by the platform rather than saved.
- Review the draft. Nothing is guest-visible yet. Check prices line by line and strip any dietary claim you didn’t provide.
- Say “publish.” The menu goes live at your venue’s URL, and the platform keeps a rollback snapshot in case you want the previous version back.
From there, maintenance is conversational: “hide the tuna tartare”, “add a summer drinks section”, “translate the new dishes into German”. The broader method comparison (built-in platform AI, free-chatbot drafting) is in our guide to creating a restaurant menu with AI.
What about Claude Code, Cursor, and the API?
Technical owners (or their developers) can skip the browser entirely: Claude Code, Cursor, and Codex connect to the same MCP endpoint with a dk_live_ API key from the Integrations page. One command in Claude Code:
claude mcp add --transport http duckhub https://mcp.duck-hub.com/mcp \
--header "Authorization: Bearer dk_live_your_api_key"
Same 39 tools, same validation, same draft-then-publish flow; the MCP documentation has the equivalent config for Cursor and Claude Desktop. This route suits agencies managing menus for several venues (one key per venue) and owners who want menu updates inside existing automation.
One Claude-specific pattern deserves a mention: the read-only key. The Integrations page can issue a key that permits every read tool and refuses every write server-side. Point Claude at it and you get a safe analyst: “which dishes have no photo?”, “compare my category structure to a typical pizzeria”, “list items missing translations”, with zero chance of an accidental edit.
Claude alone vs Claude connected
| Claude alone | Claude + menu platform (connector) | |
|---|---|---|
| Draft categories and descriptions | Yes | Yes |
| Read a menu photo or PDF | Yes | Yes, and turn it into real menu items |
| Publish a live, scannable QR menu | No | Yes |
| Update prices later | New chat, manual copy | One sentence, done |
| Analyze the menu without edit risk | n/a | Yes, via a read-only key |
| Cost | Free plan works | Free (Duckhub Egg plan + free Claude) |
Bottom line: unconnected Claude is a good menu copywriter; connected Claude is closer to a part-time menu manager. The connection is what removes the copy-paste loop between “AI wrote it” and “guests can scan it.”
Two minutes to try it: create a free Duckhub account, add the connector in Claude, and ask it to build your menu. Free plan, 0% commission, rollback included.