English Français العربية

Yuva

Official registry Search and web

Customer support inbox: search, read, triage and draft replies to e-mail and chat.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http yuva 'https://{yuva_host}/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "yuva": {
            "type": "http",
            "url": "https://{yuva_host}/mcp"
        }
    }
}
MCPB package https://github.com/productdevbook/yuva/releases/download/v0.3.1/yuva.mcpb

Environment variables

  • YUVA_URL required Your Yuva server, for example https://support.example.com
  • YUVA_API_KEY required secret A Yuva API key; its scopes and inboxes limit what the assistant can do

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Yuva
  2. Features
  3. Quick start
  4. SDKs and clients
  5. Privacy and security
  6. Documentation
  7. Community and contributing
  8. License

Yuva

One inbox for every product you run.

Website · Docs · API · Releases · Roadmap · X

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
ConversationsOne 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.
ReachMailing lists with consent records and imports, e-mail designs from templates, broadcasts with approval and reports, and a deliverability check.
PublishHelp center, documentation pages, status pages on your own domain, a roadmap board and What's new.
InsightsReports 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 inMigrations 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 itA 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

  1. Write compose.yaml and .env from the install guide.
  2. Start it:
     docker compose up -d
  3. Create the first owner:
     docker compose exec yuva /yuva bootstrap --email you@example.com --workspace "Example"
  4. 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

ForInstallGuide
Web: <yuva-chat>, headless clientnpm install useyuvaWeb widget, Headless
React and shadcn/uinpx shadcn@latest add https://useyuva.com/r/yuva-discussions.jsonshadcn registry
iOS and macOSSwift package https://github.com/productdevbook/yuva.git, product YuvaKitMobile SDKs
Androidimplementation("com.github.productdevbook:yuva:v0.1.0")Mobile SDKs
Gogo get github.com/productdevbook/yuva/sdk/goGo SDK
AI assistants/mcp on your server, or yuva.mcpb from a releaseMCP

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.

“Yuva” is Turkish for nest, or home.

Frequently asked questions

What is Yuva?

Customer support inbox: search, read, triage and draft replies to e-mail and chat.

How do I install Yuva?

It runs as a remote server. In Claude Code: claude mcp add --transport http yuva 'https://{yuva_host}/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Yuva need an API key?

Yes. It expects YUVA_URL, YUVA_API_KEY, which you set in its configuration.

Is Yuva open source?

Yes. Its code is on GitHub under the AGPL-3.0 license.

Who maintains Yuva?

It is published by productdevbook. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.