
Yuva
io.github.productdevbookv0.0.4更新於 Oct 9, 2026
Customer support inbox: search, read, triage and draft replies to e-mail and chat.
概覽
讓助理在 Yuva 收件匣中搜尋、閱讀、分類客戶支援郵件與聊天,並起草回覆。
- 功能
- 將助理連接到 Yuva 客戶訊息收件匣,使其能搜尋與閱讀支援郵件及即時聊天對話、進行分類,並撰寫草稿回覆供團隊成員寄出。Yuva 本身不執行任何模型;助理以使用者身分登入運作,API 金鑰的範圍與收件匣成員權限限制了它可存取的內容。清單未列出個別工具名稱。
- 適用情境
- 適合團隊以 Yuva 處理客戶支援,並希望助理協助整理來信對話與準備回覆草稿的情況。它針對自架的 Yuva 部署,而非通用收件匣。
- 執行需求
- 需要 Yuva 伺服器網址(YUVA_URL)與 Yuva API 金鑰(YUVA_API_KEY);金鑰的範圍與所屬收件匣決定助理能做什麼。可作為遠端端點或本機程序執行,伺服器本身需自架(一個 Go 二進位檔加 Postgres,或 Docker 映像)。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Yuva,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"yuva": {
"type": "http",
"url": "https://{yuva_host}/mcp"
}
}
}README
Yuva
One inbox for every product you run.
Open-source customer messaging: support e-mail, live chat and in-app conversations from all of your products in one shared inbox. Self-hosted, one Go binary with Postgres.
[!WARNING] Pre-alpha. The API and database schema can change without migration paths, and the code has not had an independent security audit. Try it with test data, not real customer conversations.
Why Yuva
- Every product, one inbox. Each product is an inbox with its own branding, language, hours and team. Members see only the inboxes they were given.
- Every channel, one conversation. E-mail with proper threading, live chat with the
<yuva-chat>web component, in-app messages and feedback through native iOS and Android SDKs, and an API for everything else. - Your users stay yours. Your backend signs a short-lived identity token; Yuva never sees your user database. Signed webhooks let your backend send its own push notifications.
- Headless when you want it. Scoped API keys, bots that write drafts for a member to send, an event feed and a headless JS client let you build your own inbox, chat and automations.
- Works with AI assistants. A built-in MCP server lets Claude, ChatGPT, Cursor and other assistants triage and draft replies, signed in as you with OAuth. Yuva runs no model itself.
- Small to run. One Docker image and Postgres. No Redis, no separate workers.
Quick start
- Write
compose.yamland.envfrom the install guide. - Start it:
docker compose up -d. - Create the first owner:
docker compose exec yuva /yuva bootstrap --email [email protected] --workspace "Example". - Put it behind HTTPS and sign in with the code that arrives by e-mail.
Documentation
How it is built: architecture. What is next: roadmap. What changed: changelog.
Repository
Contributing
Issues and pull requests are welcome; read CONTRIBUTING.md first. Contributions are made under the CLA. Report security issues privately as described in SECURITY.md.
License
The server and panel are AGPL-3.0; the SDKs and the API contract are MIT, so they ship inside closed-source apps without copyleft obligations. Details in LICENSING.md. The name and logo are covered by TRADEMARK.md.
來源:README.md,提交 010591b
工具
0版本歷史
1- v0.0.4最新Oct 9, 2026

