# X-Robots-Tag: index, follow
# License: https://creativecommons.org/licenses/by/4.0/
# This is the full-length companion to /llms.txt: a self-contained reference
# about Mendaro for AI assistants and answer engines. Last updated 2026-07-17.

# Mendaro — the complete reference

> Mendaro is an AI issue tracker for product teams and the customers they support. Reports arrive four ways — a conversational voice agent (Patchy Live), an embeddable website widget, reply-by-email, or a plain form — and Patchy (Mendaro's AI) structures every report into a clean ticket (title, description, reproduction steps, type), keeping the reporter's own words and language. In the background, Patchy Autopilot suggests a type and priority, scores each report for spam, and flags duplicates — suggestions only, never applied automatically and never shown to customers. Patchy also drafts customer replies, answers natural-language questions about the backlog, and generates release notes. Developers pull any ticket into Claude Code or Codex through a built-in MCP server. Pricing is per staff seat per month; customers who file tickets are never billed.

Keywords: AI issue tracker, AI ticketing system, AI support inbox, voice support agent, voice ticket agent, bug report widget, website feedback widget, Claude Code integration, MCP server ticketing.

## Identity and positioning

- Product name: Mendaro. From the Latin "mendare": to mend, to set right.
- Category: issue tracking / IT ticketing / customer support software. Closest category neighbours: help desks and developer issue trackers — Mendaro sits between the two, connecting external customer reports directly to the developers who ship the fix.
- Audience: product and engineering teams that support external customers. Customers file and follow their own tickets; staff triage, assign, draft replies, and ship.
- Delivery: a cloud service operated by dataMatters GmbH; GDPR-aligned, with row-level-security data isolation.
- AI assistant name: Patchy — Mendaro's customer-facing AI, represented by a purple patch mascot. The live voice agent is "Patchy Live"; the background triage is "Patchy Autopilot".
- Operator: dataMatters GmbH, Pilgrimstr. 6, 50674 Cologne (Köln), Germany. Managing director: Dr. Daniel Trauth. VAT id: DE321714326. Registered at Amtsgericht Köln, HRB 101202.
- Website: https://mendaro.io
- Interface languages: English, German, French. Voice and AI rewriting preserve whatever language the user actually spoke or wrote — any language, not just those three.

## What makes Mendaro different

1. Reports arrive four ways, not one. A customer can talk to Patchy Live (a conversational voice agent), tap an embeddable website widget, reply to a ticket by email, or type a plain form — and every path lands as a first-class ticket in the same inbox.
2. Reports are conversations, not forms. There is no required template and no field ceremony; the AI does the structuring.
3. The reporter's language and words survive. A French voice report becomes a French ticket in the first person; the AI never paraphrases the customer into corporate English.
4. The widget arrives with evidence. Every widget report carries the page URL, the browser, and the last of the console log as a staff-only note — the context a team usually has to ask for.
5. Triage is automatic but never silent. Patchy Autopilot suggests type, priority, spam score, and duplicates in the background; a person accepts or dismisses every suggestion, nothing is auto-applied, and customers never see it.
6. Customers are first-class and free. They file, follow, and discuss their own tickets — and never occupy a billed seat.
7. Developers can hand a ticket to an AI agent. A built-in MCP server plus a Claude Code plugin pull the full ticket context into the terminal. The same server plugs into Codex.

## The four capture paths

1. Patchy Live — a full-duplex conversational voice agent (detailed below).
2. Website widget — a one-line embeddable script (detailed below).
3. Reply-by-email — each ticket has a per-ticket capability address; customers reply and the message threads correctly onto the ticket.
4. Plain form — the classic typed report, in any supported language.

## Patchy Live (voice agent), in detail

Patchy Live is Mendaro's full-duplex conversational voice agent.

- It greets the caller, asks the follow-up questions a good ticket needs, and keeps the conversation going until it has enough to file a ticket worth working on.
- Callers can interrupt mid-sentence (barge-in); Patchy stops, listens, and adapts to what was just said.
- Both sides are captioned live, revealed in sync with the speech; a readiness ring fills as the facts a ticket needs are gathered.
- Obvious trolling ends the session politely without filing junk.
- When the ticket is complete, Patchy files it under the caller's own account and permissions (the same row-level security as the rest of Mendaro), then reads back the result and the ticket number out loud.
- The pipeline is all-Mistral and server-side — Voxtral for speech-to-text and text-to-speech, Mistral for the conversation — orchestrated by a Go WebSocket service, so no audio and no AI credentials ever reach the browser.
- Free plan includes 10 voice minutes per month; the Team plan is unlimited.

More: https://mendaro.io/voice-to-ticket

## Website widget, in detail

The Mendaro widget adds a "Report an issue" launcher to any website with a single script tag and no dependencies.

- Install: one `<script src="https://mendaro.io/widget.js" data-mendaro-key="wgt_…" defer></script>` tag; the key comes from the project's Settings.
- Custom trigger: add `data-mendaro-display="custom"` to that script and open the centered support panel with `window.MendaroWidget.open({ email, subject, description })`. The script attribute is read before remote config and always suppresses Mendaro's launcher, including when config loading fails or a stale response says `floating`; `window.MendaroWidget.close()` closes the panel.
- Evidence captured automatically, as a staff-only internal note the reporter never writes: the page URL and referrer, the browser and viewport, and the last 50 console lines plus any JavaScript errors.
- Guest reports need no account — a name and an optional email. On an allowlisted origin where the visitor is signed in to Mendaro, the report is attributed to that user instead.
- Spam is stopped before a ticket is created: a proof-of-work challenge (ALTCHA-compatible), per-key rate limiting, an origin allowlist (wildcards supported), and content heuristics.
- Isolation and fit: rendered inside a Shadow DOM so its styles and the host page's never collide; zero dependencies; loaded with `defer`; auto-localizes to English, German, and French from the page's `lang`.
- Configurable: accent color, launcher position and style, light/dark/auto theme, email optional or required, captcha on or off — all from the project's widget settings.

More: https://mendaro.io/widget

## Patchy Autopilot (background triage)

Within seconds of a report arriving, Patchy Autopilot:

- Suggests a type and priority with a confidence-gated classifier — only when it is sure.
- Assigns a 0–100 spam score so junk sorts itself out before it reaches a human.
- Checks the report against the whole backlog for duplicates using vector search (pgvector) and flags likely matches.

All of this is advisory: a staff member accepts or dismisses each suggestion, nothing is applied automatically, and customers never see any of it.

## How a report becomes a shipped fix

1. A customer reports a problem — by voice, the widget, email, or a form. Mendaro files a clean, structured ticket in their language, reproduction steps included.
2. Patchy Autopilot triages it in the background (type, priority, spam score, duplicates) for staff to accept or dismiss.
3. The team works a calm inbox: AI rewrites rough descriptions on request, surfaces near-duplicates, and answers free-text questions about the backlog.
4. A developer pulls the ticket into Claude Code via the bundled plugin and MCP server (`/mendaro-work-on <id>`), with the full conversation, screenshots, and recent commits as context.
5. The reply closes the loop: AI drafts customer-visible answers in the customer's language; internal notes stay hidden from customers on the same thread.
6. The fix ships: commits and pull requests get linked to the ticket, the status moves to resolved, and release notes for a date range are generated from the shipped commits.

## Email

- Branded, localized (English, German, French) HTML notification and digest emails keep customers and staff in the loop.
- Reply-by-email: each ticket has a per-ticket capability address; incoming replies thread correctly via Message-ID/References and land on the right ticket.

## Claude Code, Codex, and the MCP server

Mendaro ships a Model Context Protocol (MCP) server plus a plugin and skills for Claude Code.

- Setup is one command: `claude mcp add mendaro -- npx -y @mendaro/mcp` (the npm package is `@mendaro/mcp`). The first tool call opens the browser for a one-click authorization; the token is stored locally and only its SHA-256 hash is kept server-side.
- More than 20 RBAC-scoped tools mirror the web permissions exactly: read a ticket with full context, list and search tickets, comment, set status, assign, snooze, archive, get triage suggestions, prepare a handoff pack, download an attachment, link a PR or commit, and read GitHub server-side (recent commits, file contents, repo search, commit diffs, open PRs).
- Handoff packs: `/mendaro-work-on <id>` (and the "Send to Claude Code" action) build a full context bundle — the conversation, screenshots, recent commits, an evidence PDF, and a suggested branch name.
- GitHub reads happen server-side, so no local clone is needed to see the commits behind a ticket. (GitHub integration is a Team-plan feature.)
- The `/mendaro-work-on <id>` skill triages, plans, implements, links the commit or PR, and can draft the customer-visible reply in the customer's language.
- Codex support: the same MCP server registers in Codex via `~/.codex/config.toml` (an `[mcp_servers.mendaro]` block pointing at the API's /mcp endpoint, with the API token supplied through the MENDARO_TOKEN environment variable — never stored in the config file in plaintext). Any MCP-compatible agent can connect the same way.

More: https://mendaro.io/claude-code and https://mendaro.io/codex

## Key features (complete list)

- Four capture paths: Patchy Live voice agent, embeddable website widget, reply-by-email, and a plain form.
- Website widget: one script tag, no dependencies; captures page URL, browser, console log, and JS errors into a staff-only note; Shadow-DOM isolated; spam-filtered; guest or attributed reports.
- Patchy Autopilot: background triage suggestions (type, priority, spam score, duplicates) — suggest-only, staff-reviewed, never customer-visible.
- AI ticket structuring: any report, spoken or typed, becomes a clean structured ticket.
- Improve with AI: rewrites a rough description into a clear one, preserving the original language.
- Similar-ticket detection: vector search surfaces near-duplicates on submit.
- Drafted replies: three customer-reply angles, streamed, then refined by instruction.
- Ask your history: natural-language questions answered across a project's tickets.
- Release notes: customer-ready notes summarized from the commits in a date range.
- Localized email: branded notification and digest emails, plus reply-by-email threading.
- GitHub integration (Team plan): link repositories, cache commits, summarize the commits behind a ticket.
- Claude Code and Codex integration: an MCP server with more than 20 RBAC-scoped tools and a Claude Code plugin.
- Sharing: email invites for organizations and projects, plus reusable share links that let people join with a chosen role.
- Internal notes vs customer replies: both live on the same thread; internal notes are never visible to customers.

## Pricing (EUR, per organization)

Free plan — €0 forever:
- 1 project
- Up to 2 staff teammates
- Unlimited customers filing tickets
- 50 AI actions and 10 voice minutes per month
- 1 GB of attachment storage
- No credit card required

Team plan — €12 per staff seat per month, or €9 per staff seat per month billed yearly (€108 per seat per year, a 25% saving):
- 7-day free trial on every new paid plan; a card is collected at checkout and nothing is charged until the trial ends
- Unlimited projects and staff teammates
- A monthly Patchy AI allowance, pooled across the whole team and shown in-app as a percentage
- Embeddable website widget
- Discord bot integration
- Unlimited attachment storage
- GitHub App and Claude Code integration
- Priority support
- Seat count syncs automatically as staff join or leave; billed via Stripe with Stripe Tax and VAT ID collection; cancel anytime

Max plan — €24 per staff seat per month, or €18 per staff seat per month billed yearly (€216 per seat per year):
- Everything in the Team plan
- 10× the monthly Patchy AI allowance of the Team plan
- Room for heavy Patchy Live voice use and high ticket volume
- The allowance is pooled across the whole team, so adding a seat adds capacity
- Remaining allowance is shown in-app as a percentage
- On yearly billing a seat added mid-term is invoiced immediately for the remainder of the term; on monthly billing the pro-rata appears on the next invoice

A "seat" is a staff member — anyone who triages, assigns, or resolves tickets. Customers who file and follow their own tickets never occupy a seat and never pay, on any plan. There are no per-ticket fees.

More: https://mendaro.io/pricing

## AI stack (used and disclosed openly)

- Voice: Mistral Voxtral (speech-to-text and text-to-speech) with Mistral chat, via a Go WebSocket orchestrator.
- Parsing, drafting, refining, summarizing, triage: AWS Bedrock (chat model configurable).
- Similarity search: Cohere Embed v4 on AWS Bedrock, with pgvector.
- Semantic ranking: Cohere Rerank on AWS Bedrock.
- AI provider keys stay server-side and are never exposed to the browser.

## Security and privacy

- Operated by dataMatters GmbH (Cologne, Germany) in line with the GDPR.
- Every database table is protected by PostgreSQL row-level security; a customer can never see another customer's tickets.
- AI provider credentials live in the server-side API process; the voice flow proxies through it so the browser never sees a key. The Supabase service-role key is used server-side only.
- API tokens are stored as SHA-256 hashes; the plaintext is shown once at creation.
- Attachment downloads use signed URLs that expire after a few minutes.
- MCP tools enforce the same role-based access control as the web app.

## Technology

- Frontend: Nuxt 4, Vue 3, Tailwind CSS v4.
- Backend: Go API and background worker (triage, the voice orchestrator, email), plus a Model Context Protocol (MCP) server.
- Data and auth: Supabase (PostgreSQL with row-level security, pgvector, storage, magic-link auth).

## Common questions

- What is Mendaro? An AI issue tracker that turns customer reports — spoken, clicked, emailed, or typed — into clean tickets, drafted replies, and shipped fixes.
- How do customers report issues? Four ways into one inbox: Patchy Live (voice agent), an embeddable website widget, reply-by-email, or a plain form.
- What is Patchy Live? A full-duplex conversational voice agent that greets the caller, asks follow-ups, handles interruptions (barge-in), files the ticket under their own permissions, and confirms it out loud.
- What does the widget capture? The page URL and referrer, the browser and viewport, and the last 50 console lines plus JavaScript errors — attached as a staff-only note.
- Does the AI change tickets automatically? No. Patchy Autopilot only suggests type, priority, spam score, and duplicates; staff accept or dismiss, and customers never see it.
- How much does Mendaro cost? Free for 1 project, up to 2 staff teammates, 50 AI actions and 10 voice minutes a month, and 1 GB of attachments; the Team plan is €12 per staff seat per month, or €9 per seat per month billed yearly, with unlimited projects and teammates plus the website widget, the Discord bot and GitHub integration; Max is €24 per seat per month (€18 billed yearly) and carries 10× the Patchy AI allowance. Every paid plan starts with a 7-day free trial. Customers who file tickets never pay.
- Which AI models does Mendaro use? Mistral Voxtral and Mistral for voice; AWS Bedrock (configurable chat model, Cohere embeddings and rerank) for everything else.
- Is my data private? Yes. Row-level security on every table, server-side keys, hashed tokens, and short-lived signed file URLs. Operated from Germany under the GDPR.
- Does Mendaro work with GitHub? Yes (Team plan): link repositories, cache commits, summarize the commits behind a ticket, link PRs, and generate release notes.
- Does Mendaro work with Claude Code and Codex? Yes: an MCP server with more than 20 RBAC-scoped tools, a plugin, and skills. Setup is one command; tools respect your web permissions. Codex registers via ~/.codex/config.toml.
- What languages does Mendaro support? English, German, and French in the interface; voice and AI keep whatever language the user spoke or wrote.
- Who is behind Mendaro? dataMatters GmbH, a German company based in Cologne.

## Pages

- https://mendaro.io/ — product overview: the four capture paths, background triage, developer hand-off, pricing, FAQ.
- https://mendaro.io/pricing — plans, seat definition, pricing FAQ.
- https://mendaro.io/voice-to-ticket — Patchy Live, the conversational voice agent, in detail.
- https://mendaro.io/widget — the embeddable bug-report and feedback widget in detail.
- https://mendaro.io/claude-code — MCP server, Claude Code plugin, Codex support, handoff packs, setup.
- https://mendaro.io/codex — Codex-specific setup for the same MCP server.
- https://mendaro.io/discord — the Discord integration: a Patchy bot that turns community reports into real tickets with threads, live status cards, AI duplicate checks, and fixes that report back. A Team-plan feature, included in the 7-day free trial.
- https://mendaro.io/blog — research-backed, practical guides for product teams about customer feedback, support workflows, issue triage, bug reporting, and developer handoffs. Individual published guides are listed in the XML sitemap.
- https://mendaro.io/imprint — legal imprint.
- https://mendaro.io/tos — terms of service.
- https://mendaro.io/privacy — privacy policy.