domailo
Sign inStart trial

An email MCP server for developers: bug reports and replies in the terminal

Quick answer: With Domailo connected to Claude Code, the assistant reads the customer's report in support@, opens the attached log (TXT, CSV or XML) with ler_anexo, investigates the code in the same terminal and drafts the reply to the customer with salvar_rascunho. If you also connect GitHub's MCP server, the same request can open the issue.

  • Read and write
  • Checked on October 17, 2026

Who it is for

For small product teams where the person who codes also reads support: the technical founder, the developer of a small SaaS, the maintainer who gets reports at contact@.

The gain is not switching context: the report, the log, the code and the reply stay in the same conversation. Domailo handles the email side; the repository, issues and deploys stay with the tools you already use.

What it looks like

domailoconnected via MCPExample with fictional data

Request: Read the latest email in support@example.com about an export error, open the attached log, find the cause in this repository's code and draft a reply to the customer explaining what we will fix.

  • listar_emailscaixa: "support@example.com" · busca: "export"1 conversation
  • ler_email2 messages · 1 attachmentread
  • ler_anexoexport-error.txttext
  • salvar_rascunhoconversa · para: the customersaved

The log shows a timeout when exporting reports with more than 10,000 rows. The query in src/export/csv.ts loads everything at once. I left a reply in Drafts:

  • Causeunpaginated query during export
  • Fixexport in batches of 1,000 rows (proposed in this repository)
  • Replydraft in support@, no deadline promised

Step by step

  1. Connect Domailo to Claude Code with a personal key (see the Claude Code guide).
  2. Open Claude Code in the project folder, so the same assistant sees both the code and the email.
  3. Ask for the investigation starting from the email: the assistant finds the conversation, reads the history and opens the text attachments.
  4. Review the cause and the fix as you would any assistant suggestion. The reply to the customer stays in Drafts until you send it.

Ready-to-copy prompts

Swap the addresses and names for yours. The more specific the request (mailbox, time period, what the reply must say), the better the result.

  • List the bug reports that came into support@example.com this week and group them by feature.
  • Open the logs attached to the last three bug reports and tell me whether they are the same problem.
  • Based on this commit, draft for each customer who reported the bug a reply saying the fix has shipped. Don't send them.
  • Summarize the feature requests that came into contact@example.com in the last month.

How it changes by type of business

Small SaaS
Support and product in the same person: report → log → fix → reply, without leaving the terminal.
Dev shop
Each client has a support mailbox; the assistant summarizes reports per client before the weekly meeting.
Project with several MCP servers
Domailo handles email; GitHub, a database or monitoring come in as other MCP servers in the same client. The assistant combines the results.

Permissions needed

  • "Read and write" access. Tools used: listar_emails, ler_email, ler_anexo, salvar_rascunho.
  • Admins, and people an admin allowed to use AI assistants. Each person sees only the mailboxes they already open in the webmail.
  • Included in the Startup, Essential and Team plans and during the trial.

Caveats and limits

  • Domailo does not integrate with GitHub or other tools: the assistant is what combines the MCP servers.
  • Domailo's MCP does not notify the assistant when an email arrives. The conversation starts with you or with a script you run.
  • Emails and logs are third-party content and may carry hidden instructions. Do not approve terminal commands suggested from an email's text without reading what they do.
  • ler_anexo reads .txt, .csv and .xml as text (up to 100,000 characters), plus PDF and images. .log or .zip files can only be downloaded in the webmail.
  • We tested with Claude Code. Other clients that accept a remote MCP server with an authorization header should work with the same key.

Frequently asked questions

What is an email MCP server?

A service that exposes email as tools for AI assistants through the Model Context Protocol. Domailo's lives at https://domailo.app/mcp and has 26 tools: list, read, read attachments, draft, send, schedule, organize and, for admins, manage domains, mailboxes and the team.

Do I need to host anything?

No. The server is remote and already running. You only add the address and the key to your MCP client.

Does it work with Cursor?

Clients that accept a remote HTTP MCP server with an authorization header use the same key and the JSON configuration shown under Settings › AI integrations. So far we have tested Claude and Claude Code.

Can the key live in the repository?

No. The key gives access to email as if it were you. Keep it out of the code (environment variable or the client's local configuration) and revoke it if it shows up anywhere.