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 分