DuckHub QR Menu

com.duck-hub由 duck-hub.com 發布官方發布者v1.0.2更新於 Oct 27, 2026

Hosted MCP server to manage a restaurant menu from AI agents - 39 tools over the DuckHub API.

已驗證Streamable HTTP可網頁執行效率與工作流商業與電商媒體與設計

概覽

AI 產生的概覽

託管型 MCP 伺服器，讓 AI 助理讀取並編輯 DuckHub 餐廳菜單，涵蓋商品、分類、選項、價格、圖片、翻譯、促銷與訂單。

可以做什麼
  • 讀取菜單：參考資料、菜單、商品、分類、發布紀錄與稽核日誌
  • 建立菜單：批次同步，新增或刪除商品與選項群組
  • 調整設定、上傳商品圖、橫幅與標誌圖片，管理多語翻譯
  • 管理促銷、橫幅與桌位，並發布、回復或清理菜單
  • 在付費方案下查看與更新訂單
適用情境
適合餐廳團隊想用對話方式草擬、翻譯、配圖或重整 DuckHub 菜單，或查看與更新訂單，而不必在 DuckHub 應用程式裡手動操作。
執行需求
遠端託管端點，採 Streamable HTTP，無需安裝。需要 DuckHub 帳號，並以 Authorization Bearer 標頭提供 dk_live_ API 金鑰，或在 claude.ai 與 ChatGPT 使用 OAuth 登入。Claude Desktop 需透過 mcp-remote 橋接，依賴 Node.js。訂單工具需要付費方案。
安裝前請注意
寫入類工具會改動線上餐廳資料：publish_menu 會讓草稿對顧客可見，cleanup_menu 的陣列是保留清單，未列出的項目會被隱藏或刪除，刪除工具會移除商品與選項群組。建議先使用 dryRun，僅做分析的助理請改用唯讀金鑰。API 金鑰是完整權限的機密；OAuth 一次只對應一個門市。方案限制、速率限制與稽核日誌照常適用。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 DuckHub QR Menu，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.duck-hub%2Fmenu/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "duckhub-qr-menu": {
      "type": "http",
      "url": "https://mcp.duck-hub.com/mcp"
    }
  }
}

README

DuckHub MCP Server — restaurant menu management for AI agents

Hosted MCP (Model Context Protocol) server for DuckHub. Manage a restaurant's menu — products, categories, modifiers, prices, images, translations, promotions, orders — straight from Claude, Cursor, or any MCP-capable AI agent. One URL, your dk_live_ API key, 39 ready-made tools. No install, no code — the server is hosted by DuckHub.

[MCP] [Transport] [Hosted] [Auth] [Docs] [Glama quality]

What is this?

DuckHub is a SaaS platform for restaurants: digital menus, contactless ordering, table reservations and delivery. The DuckHub MCP server exposes the DuckHub v1 REST API to AI agents as typed tools. Instead of writing HTTP requests, your agent sees build_menu, set_image, publish_menu and can build and manage a full menu from a conversation.

The server is remote / hosted — there is nothing to install or run. You add one URL to your AI client and authenticate with the same dk_live_ API key the REST API uses.

Endpoint

POST https://mcp.duck-hub.com/mcp

If the mcp. subdomain is not yet resolvable in your network, the same server is also reachable at https://api.duck-hub.com/mcp.

  • Transport: Streamable HTTP (stateless)
  • Auth: Authorization: Bearer dk_live_... header (API key from the DuckHub app → Integrations page)
  • All the usual rate limits, plan limits and the audit log apply unchanged.

Connect your client

Get your API key from the DuckHub app → Integrations, then:

Claude Code

bash
claude mcp add --transport http duckhub https://mcp.duck-hub.com/mcp \  --header "Authorization: Bearer dk_live_your_api_key"

Cursor — .cursor/mcp.json

json
{  "mcpServers": {    "duckhub": {      "url": "https://mcp.duck-hub.com/mcp",      "headers": { "Authorization": "Bearer ${env:DUCKHUB_API_KEY}" }    }  }}

Claude Desktop — claude_desktop_config.json

Desktop connects remote servers through the mcp-remote bridge (needs Node.js):

json
{  "mcpServers": {    "duckhub": {      "command": "npx",      "args": [        "mcp-remote",        "https://mcp.duck-hub.com/mcp",        "--header",        "Authorization: Bearer dk_live_your_api_key"      ]    }  }}

Claude API — MCP connector block

json
{  "mcp_servers": [    {      "type": "url",      "url": "https://mcp.duck-hub.com/mcp",      "name": "duckhub",      "authorization_token": "dk_live_your_api_key"    }  ]}

claude.ai (web) & ChatGPT — OAuth

claude.ai and ChatGPT connect custom MCP servers through OAuth (there is no API-key field). Add DuckHub as a custom connector with the URL:

https://mcp.duck-hub.com/mcp

then Sign in to DuckHub, choose the venue to connect, and approve. The flow uses OAuth 2.1 with PKCE — your DuckHub login authorizes access and no API key is stored in the client. One DuckHub account maps to one connected venue at a time (reconnect from the DuckHub app to switch venues).

Read-only access

The Integrations page can also issue a read-only key (same dk_live_ format). With it every read tool works normally, and every write tool fails with 403 READ_ONLY_KEY — the API refuses the write before touching anything. Write tools are also marked with standard MCP annotations (readOnlyHint / destructiveHint), so well-behaved clients can filter or confirm them. Use a read-only key for agents that should analyse the menu but never change it.

The 39 tools

All tools wrap the v1 REST API — same behavior, same limits.

GroupTools
Discover & readget_reference, get_menu, list_products, get_product, list_categories, list_publications, get_audit_log
Build the menubuild_menu (bulk sync), set_product, delete_product, set_modifier_group, delete_modifier_group, list_modifier_groups
Settingsget_settings + 7 task-scoped update_* tools
Mediaset_image — product / banner / logo
Translationsset_translations, get_translations
Merchandisingpromotions / banners / tables — list_* / set_* / delete_*
Go livepublish_menu, rollback_publish, cleanup_menu
Orders (paid plans)list_orders, get_order, update_order_status

Agents should call get_reference first: it returns every allowed enum value, the venue's plan limits and current usage, and the money conventions.

Things agents get wrong

  • Money is integers in minor units — 12.50 is sent as 1250 (cents).
  • Nothing is guest-visible until you publish. build_menu edits the draft; publish_menu makes it live (with a rollback snapshot).
  • Dry-run first. build_menu and cleanup_menu accept dryRun: true.
  • cleanup_menu arrays are KEEP-lists — anything not listed is hidden/deleted.
  • Orders tools need a paid plan — else 403 PAID_PLAN_REQUIRED.

Full documentation

→ docs.duck-hub.com/mcp — connection guide, per-tool reference, error envelope, rate/plan limits.

About / support

License

MIT — see LICENSE. This repository contains documentation and the server manifest only; the MCP server itself is hosted by DuckHub.

來源：README.md，提交 81b425a

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.2最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分