Customer support inbox: search, read, triage and draft replies to e-mail and chat.
io.github.productdevbook/yuva — Model Context Protocol (MCP) Server
The io.github.productdevbook/yuva MCP server provides a customer support inbox workflow. It supports searching, reading, triaging, and drafting replies to both email and chat. The server description is limited to these capabilities and does not provide additional tool or configuration details.
🛠️ Key Features
Search customer support inbox content
Read messages
Triage incoming emails and chat
Draft replies for email and chat
🚀 Use Cases
Locating relevant support messages via search
Reviewing message details for support handling
Classifying/prioritizing tickets through triage
Producing draft responses for follow-up
⚡ Developer Benefits
Consolidates common inbox actions: search, read, triage, and reply drafting
Handles both email and chat contexts
⚠️ Limitations
Available details do not include tool count, endpoints, authentication, or integration specifics
Yuva is open-source customer messaging for teams that run several products. Support e-mail, live
chat, in-app messages and feedback from every product land in one shared inbox, next to the
newsletters, help center, status pages and analytics you send and publish from the same place.
You host it yourself: one Docker image and Postgres.
WARNING
Beta. The API can still change before 1.0, so read the release notes before you
upgrade. Database migrations run when the server starts: back up
first. The code has not had an independent security audit.
Features
Conversations
One inbox per product with its own branding, language, hours and team. E-mail, live chat, in-app messages and app feedback in one thread, with notes, labels, mentions and bot drafts a member reviews.
Team mail
Shared addresses such as sales@ and people's own mailboxes in the same inbox, with drafts, send later, filters and search operators. Personal mailboxes are private, and you can delegate them. Yuva is the mailbox; it is not an IMAP server for mail apps.
Reports on opened and closed conversations, response times, SLA and ratings, cookieless analytics for websites and apps, and a support report that ranks pages by the conversations they cause.
Move in
Migrations of history and live mail from Gmail, Microsoft 365, Yandex, iCloud, Zoho, any IMAP server, Zendesk, Help Scout and Front. The old mailbox is only read.
Read CONTRIBUTING.md first; contributions are made under the CLA.
For a local server with Postgres and Mailpit, which catches every mail it sends, run
docker compose -f deploy/compose.yaml up -d.
Ask questions and report bugs in issues, and follow
@useyuva for news.
License
The server and panel are AGPL-3.0. The SDKs (sdk/) and the API contract (openapi/)
are MIT, so you can ship them in closed-source apps. Details in
LICENSING.md; name and logo in TRADEMARK.md.
“Yuva” is Turkish for nest, or home.
Install
Remote endpoint
Streamable HTTP
Hosted server - connect over the network, no local install.
url
https://{yuva_host}/mcp
Configuration
Environment variables
YUVA_URLrequired
Your Yuva server, for example https://support.example.com
YUVA_API_KEYrequiredsecret
A Yuva API key; its scopes and inboxes limit what the assistant can do