D
David-Cabeza/OpenCovers
Open-source reservations engine for restaurants, with an HTTP API and an MCP server
★ 2·更新 2026-11-19
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
装完之后怎么算装好了
- 装完该看到什么 — 命令正常结束时退出码为 0,终端里没有 "command not found" 或 "permission denied"。
- 一行自检 — 按该仓库 README 里给出的最小用法跑一次;能按 README 的描述输出就是通了。
- 答不出来怎么办 — 这个项目没有写排错说明,去仓库的 Issues 搜 install。
安装命令取自该仓库;以上判据只描述可观察到的结果,不替代项目自己的文档。
- ★ 数取值
- 2 ★ · David-Cabeza/OpenCovers · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
- 收录与活跃
- 收录于 2026-11-17 · 最近见到 2026-11-20 · 共见到 4 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 2 ★ · 2 个来源 · repo
- 安装
- 安装命令见上方「安装与配置」。
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
David-Cabeza/OpenCovers;我们收录于 2026-11-17;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# OpenCovers
以下摘录自该仓库的 README(片段)
The open-source reservations engine for restaurants — availability, bookings, tables, and the event feed, with an API and an MCP server.
Pre-alpha: it runs locally with tests, nothing is deployed yet. Public site: opencovers.dev .
## Why
Most booking systems are tied to a CRM, a point-of-sale system, or a single vendor. A venue that changes its front end or its messaging provider risks losing its reservation book.
OpenCovers keeps the book independent. Any platform or AI agent reads availability, creates a booking, modifies it, or cancels it through the same contract — and the no-double-booking rule is enforced by the database, not by application code.
## Features
### 📅 Availability and booking
Read free time slots per service, create a booking against specific tables, and move, cancel, or seat it. Every write carries an idempotency key and a monotonic version.
### 🚫 No double bookings, guaranteed
A GiST exclusion constraint in PostgreSQL rejects overlapping table allocations. It holds for any number of concurrent writers — no application-level locking.
### 🔑 Humans and machines, both first-class
Staff sign in with Better Auth and get a per-venue role. Platforms and AI agents use scoped API keys (read/write) that a venue admin mints and revokes from the staff app.
### 🎛️ Control of the room and the book
An explicit overbooking ceiling per venue (default 0, enforced under a per-venue lock), a booking note of up to 500 characters, a reconfirmation status on each reservation, and a rule that a reservation cannot be seated without a table. The staff app has a pre-shift view for a service and date, and an endpoint explains why a slot is closed.
### 👥 Staff access you control
A venue admin invites staff and removes members from the staff app, with the roles read, write, and admin applied to keys and sessions. Sign-up is controlled with the SIGNUP setting, only the owner creates venues on closed instances, and sign-in, sign-up and invitation redemption are rate limited.
### 🤖 An MCP server
The 18-tool catalog (reservation., waitlist., venue.) is exposed over stdio, so Claude, Cursor, and other MCP hosts can operate a venue directly. It is published on npm as @opencovers/mcp and listed in the official MCP registry as io.github.David-Cabeza/opencovers. Run it with npx -y @opencovers/mcp.
### 🧭 The room, covered
Walk-ins, a waitlist, zones, and automatic table assignment. The engine seats guests now, holds them in a queue, and assigns tables so platforms and agents never think about floor plans.
### 🪑 A visual floor plan
Drag tables and room elements onto a floor, snap them to a grid, rotate them, and resize them. Tables come in round, square, and rectangle shapes with chairs; room elements (bar, kitchen, wall, window, door, plant, counter, entrance) are drawn as architectural symbols on a wood floor — so the plan reads like a plan, not a list.
### 📧 Email confirmations
Confirmations, cancellations, and booking notices via Resend — one per reservation version, never duplicated. Each venue brings its own Resend account, and it's off until enabled.
### 🔔 Signed webhooks
Register an HTTPS endpoint and the engine pushes every reservation event to it: created, modified, cancelled, seated, attended, no_show, and erased. Each POST is signed with HMAC-SHA256, arrives in order, and is retried with backoff until acknowledged. Private and metadata addresses are refused. See docs/contract/webhooks.md.
Pre-alpha: it runs locally with tests, nothing is deployed yet. Public site: opencovers.dev .
## Why
Most booking systems are tied to a CRM, a point-of-sale system, or a single vendor. A venue that changes its front end or its messaging provider risks losing its reservation book.
OpenCovers keeps the book independent. Any platform or AI agent reads availability, creates a booking, modifies it, or cancels it through the same contract — and the no-double-booking rule is enforced by the database, not by application code.
## Features
### 📅 Availability and booking
Read free time slots per service, create a booking against specific tables, and move, cancel, or seat it. Every write carries an idempotency key and a monotonic version.
### 🚫 No double bookings, guaranteed
A GiST exclusion constraint in PostgreSQL rejects overlapping table allocations. It holds for any number of concurrent writers — no application-level locking.
### 🔑 Humans and machines, both first-class
Staff sign in with Better Auth and get a per-venue role. Platforms and AI agents use scoped API keys (read/write) that a venue admin mints and revokes from the staff app.
### 🎛️ Control of the room and the book
An explicit overbooking ceiling per venue (default 0, enforced under a per-venue lock), a booking note of up to 500 characters, a reconfirmation status on each reservation, and a rule that a reservation cannot be seated without a table. The staff app has a pre-shift view for a service and date, and an endpoint explains why a slot is closed.
### 👥 Staff access you control
A venue admin invites staff and removes members from the staff app, with the roles read, write, and admin applied to keys and sessions. Sign-up is controlled with the SIGNUP setting, only the owner creates venues on closed instances, and sign-in, sign-up and invitation redemption are rate limited.
### 🤖 An MCP server
The 18-tool catalog (reservation., waitlist., venue.) is exposed over stdio, so Claude, Cursor, and other MCP hosts can operate a venue directly. It is published on npm as @opencovers/mcp and listed in the official MCP registry as io.github.David-Cabeza/opencovers. Run it with npx -y @opencovers/mcp.
### 🧭 The room, covered
Walk-ins, a waitlist, zones, and automatic table assignment. The engine seats guests now, holds them in a queue, and assigns tables so platforms and agents never think about floor plans.
### 🪑 A visual floor plan
Drag tables and room elements onto a floor, snap them to a grid, rotate them, and resize them. Tables come in round, square, and rectangle shapes with chairs; room elements (bar, kitchen, wall, window, door, plant, counter, entrance) are drawn as architectural symbols on a wood floor — so the plan reads like a plan, not a list.
### 📧 Email confirmations
Confirmations, cancellations, and booking notices via Resend — one per reservation version, never duplicated. Each venue brings its own Resend account, and it's off until enabled.
### 🔔 Signed webhooks
Register an HTTPS endpoint and the engine pushes every reservation event to it: created, modified, cancelled, seated, attended, no_show, and erased. Each POST is signed with HMAC-SHA256, arrives in order, and is retried with backoff until acknowledged. Private and metadata addresses are refused. See docs/contract/webhooks.md.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/david-cabeza-opencovers/)
- 来源
- github · https://github.com/David-Cabeza/OpenCovers
- 按领域浏览
- 开源项目
- Traction
- 2 ★
- 收录来源
- 2 个独立来源
- 收录于
- 今天
更多条目
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。