About Yuva
Yuva is an open-source customer messaging platform for teams managing support across multiple products. It combines shared inboxes with publishing, mailing, and analytics, and can be hosted on the team's own servers.
Key features
- 01Shared inboxes for email and chat
- 02Team mailboxes with search and drafts
- 03Mailing lists and campaign reports
- 04Help center and status publishing
- 05Conversation and website analytics
- 06REST API, webhooks, and MCP server
Use cases
- 01Triage support conversations across products
- 02Draft and review customer replies
- 03Publish help and status pages
- 04Analyze response times and support trends
MCP support
Yuva includes an MCP server with OAuth for AI assistants such as Claude, Cursor, and VS Code. It can expose customer messaging capabilities to connected assistants.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://{yuva_host}/mcpclaude mcp add --transport http productdevbook-yuva https://{yuva_host}/mcp{"mcpServers":{"productdevbook-yuva":{"type":"http","url":"https://{yuva_host}/mcp"}}}Open in Cursor{"servers":{"productdevbook-yuva":{"type":"http","url":"https://{yuva_host}/mcp"}}}Open in VS Code{"mcpServers":{"productdevbook-yuva":{"type":"http","url":"https://{yuva_host}/mcp"}}}{"mcpServers":{"productdevbook-yuva":{"serverUrl":"https://{yuva_host}/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEYuva 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. |
| Reach | Mailing lists with consent records and imports, e-mail designs from templates, broadcasts with approval and reports, and a deliverability check. |
| Publish | Help center, documentation pages, status pages on your own domain, a roadmap board and What's new. |
| Insights | 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. |
| Build on it | A REST API with scoped keys, signed webhooks, identity tokens, headless mode, and an MCP server with OAuth for Claude, Cursor, VS Code and other assistants. |
Built with Go, Postgres and a React panel, shipped as one Docker image.
|
|
| |
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.
On Kubernetes, install the Helm chart oci://ghcr.io/productdevbook/charts/yuva; see
Kubernetes with Helm.
SDKs and clients
| For | Install | Guide |
|---|---|---|
Web: <yuva-chat>, headless client | npm install useyuva | Web widget, Headless |
| React and shadcn/ui | npx shadcn@latest add https://useyuva.com/r/yuva-discussions.json | shadcn registry |
| iOS and macOS | Swift package https://github.com/productdevbook/yuva.git, product YuvaKit | Mobile SDKs |
| Android | implementation("com.github.productdevbook:yuva:v0.3.1") | Mobile SDKs |
| Go | go get github.com/productdevbook/yuva/sdk/go | Go SDK |
| AI assistants | /mcp on your server, or yuva.mcpb from a release | MCP |
Working projects are in examples.
Privacy and security
- You host it: conversations, contacts and files stay on your servers.
- Analytics set no cookies and keep no cross-site identifiers; see analytics privacy.
- Every subscription records who consented, when and where, and lists export with that record.
- For assistants, customer text is marked as untrusted data, and their replies are drafts unless you allow sending.
- Report vulnerabilities privately as described in SECURITY.md.
Documentation
Guides, the API reference and examples are at useyuva.com/docs, and in docs/ (also in Turkish and German). How it is built: architecture. What is next: roadmap. What changed: GitHub Releases.
Community and contributing
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.