Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Beschreibung vom Entwickler (englisches Original)
Send email and newsletters with Mailtea over MCP, plus skills for email and website design.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://api.mailtea.app/mcpFühre das in deinem Terminal aus
claude mcp add --transport http mailtea https://api.mailtea.app/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"mailtea": {
"url": "https://api.mailtea.app/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"mailtea": {
"type": "http",
"url": "https://api.mailtea.app/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://api.mailtea.app/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain mailtea.app bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.10.0) kam vor 31 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Vexa, emailmd, MCP WhatsApp Cloud
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Send email and newsletters. Just ask.
Mailtea lets your AI assistant send and schedule email, check delivery, write and design newsletters, manage contacts, and build your publication's website, all from a conversation. It is for newsletter writers, creators and teams who send with Mailtea, and for developers who want an agent to handle email without writing integration code.
167 tools, grouped by what they work on:
| Tool family | What your assistant can do |
|---|---|
Email (email.*) | Send, batch, schedule, cancel and resend email, check it before sending, track delivery and engagement, and read and reply to inbound mail |
Newsletters (issue.*, monetize.*) | Draft, edit, preview, test, schedule and send newsletters, publish them to your website, follow delivery progress, and manage sponsor offers |
Templates (template.*) | Create, render, publish, duplicate and version reusable email templates |
Audience (contact.*, contact_property.*, segment.*, topic.*, suppression.*) | Manage contacts and their properties, import a CSV, build segments and topics, handle suppressions, and run referral milestones |
Automations (automation.*, automation_run.*, event.*, event_definition.*) | Build, validate, preview, enable and measure multi-step automations, and send the custom events that start them |
Website (site.*, section.*) | Edit pages, sections, navigation, footer, theme and design brief, manage images, and publish your publication's website |
Sending setup (domain.*, sender.*) | Add and verify sending and tracking domains, and manage senders |
Analytics (analytics.*) | Newsletter performance, trends, poll results and CSV exports |
Account (publication.*, api_key.*, webhook.*, auth.*) | List and create publications, connect custom website domains, manage API keys and webhooks, and check who is connected |
Your assistant picks the relevant skill from your request. You can also name a skill if you want to be explicit.
| Included skill | What it helps you do | Try saying |
|---|---|---|
Mailtea email (mailtea-email) | Send or schedule email, check delivery, draft newsletters, and manage contacts | “Help me send my first email.” |
Mailtea email design (mailtea-email-design) | Design welcome emails, newsletters, and reusable templates for real inboxes | “Draft a welcome email with one clear call to action. Do not send it yet.” |
Mailtea website design (mailtea-site-design) | Build or restyle your publication's website, with changes saved as drafts | “Draft an About page for my publication. Do not publish it yet.” |
The plugin does not replace Mailtea Studio, or the SDKs and CLI for application code. Use it when an AI assistant should do the work for you.
| Where you use AI | How to connect |
|---|---|
| Claude.ai | Settings, then Connectors, then Add custom connector, and paste https://api.mailtea.app/mcp |
| Claude Desktop | Install Mailtea from Discover, or add the same custom connector as on Claude.ai |
| Claude Code | claude plugin marketplace add mailtea-app/mailtea-agent-plugin, then claude plugin install mailtea@mailtea |
| Cursor | Settings, then Plugins, then Add from repository: mailtea-app/mailtea-agent-plugin |
| VS Code | Command Palette, then MCP: Browse servers, then Mailtea |
| Codex | codex plugin marketplace add mailtea-app/mailtea-agent-plugin, then codex plugin add mailtea@mailtea |
More clients, and a one-line install for each, are under Get started.
The first time you connect, you sign in to Mailtea in your browser, pick one publication, and choose an access level from read only to full access. Your assistant can act only inside that publication at that level, and you can revoke the connection in Mailtea at any time.
Docs · Support · Privacy policy · Terms of service
You need a Mailtea account. Sending also needs a verified sending domain. The hosted connection needs no API key, no Node.js install, and no code. You sign in through your browser.
| Client | Install |
|---|---|
| Any client | npx plugins add mailtea-app/mailtea-agent-plugin |
| Codex | codex plugin marketplace add mailtea-app/mailtea-agent-plugin then codex plugin add mailtea@mailtea |
| Claude Code | claude plugin marketplace add mailtea-app/mailtea-agent-plugin then claude plugin install mailtea@mailtea |
| Cursor | Settings → Plugins → Add from repository, or npx plugins add mailtea-app/mailtea-agent-plugin -t cursor |
| Grok Bot (in Cursor) | Installs with the Cursor plugin above; no separate step |
| VS Code / GitHub Copilot | Command Palette → MCP: Browse servers, or npx plugins add mailtea-app/mailtea-agent-plugin -t vscode |
| Kiro | MCP settings → add server, or npx plugins add mailtea-app/mailtea-agent-plugin -t kiro |
| Grok Build | /marketplace, add mailtea-app/mailtea-agent-plugin, then install mailtea |
| Gemini CLI | gemini extensions install https://github.com/mailtea-app/mailtea-agent-plugin |
| OpenCode | Add the MCP server https://api.mailtea.app/mcp (type remote) in opencode.json, then run opencode mcp auth mailtea |
| GitHub Copilot CLI | copilot mcp add mailtea https://api.mailtea.app/mcp, then connect from an interactive session |
| Windsurf | Settings → Cascade → MCP servers → add https://api.mailtea.app/mcp |
| Claude.ai | Settings → Connectors → Add custom connector → https://api.mailtea.app/mcp |
| ChatGPT | Settings → Connectors → Add → https://api.mailtea.app/mcp (Developer mode) |
| Kiro (one click) | |
| Cline | MCP Servers, then Configure MCP Servers: add the Cline entry from Manual configuration |
| Zed | Add the Zed entry from Manual configuration to settings.json |
| Warp | Settings, then Agents, then MCP servers: paste the Warp entry from Manual configuration |
| JetBrains AI Assistant | MCP settings: add the JetBrains entry from Manual configuration. It has no browser sign-in yet, so it sends a personal access token. Junie signs in through the browser itself |
| Amazon Q Developer CLI | Add the Amazon Q entry from Manual configuration to your agent configuration, then run /mcp in a session to sign in |
| Devin, Perplexity, Mistral Le Chat, Manus | Add a custom MCP connector with the URL https://api.mailtea.app/mcp |
npx plugins add is the universal path. The plugins CLI reads this package's plugin.json and installs it into whichever agent tools it detects: Claude Code, Cursor, Codex, Grok Build, Kimi Code, GitHub Copilot CLI, and VS Code. Use -t to pick one, and npx plugins targets to see what it found.
Then open a new session, connect Mailtea through the browser sign-in prompt, choose your publication and the access you want to grant, and paste:
Help me send my first email with Mailtea. Check my setup and guide me through anything missing.
Your agent checks the publications, senders, and domain verification available to your account, and explains the next step for anything missing. You do not need to know tool names or pick a skill.
Need an account? Start with Mailtea. Need a sending domain? Domain setup.
Every entry points at the same hosted server, https://api.mailtea.app/mcp. Unless a row above says otherwise, you sign in through your browser the first time the client connects, and there is no key to paste.
Cline (cline_mcp_settings.json):
{"mcpServers": {"mailtea": {"type": "streamableHttp", "url": "https://api.mailtea.app/mcp"}}}
Zed (settings.json):
{"context_servers": {"mailtea": {"url": "https://api.mailtea.app/mcp"}}}
Warp (Settings, then Agents, then MCP servers):
{"mailtea": {"url": "https://api.mailtea.app/mcp"}}
JetBrains AI Assistant: it cannot sign in through the browser yet, so send a Mailtea personal access token (create one in Settings → API keys) as the Authorization header. Junie signs in through the browser and needs no header.
{"mcpServers": {"mailtea": {"url": "https://api.mailtea.app/mcp", "headers": {"Authorization": "Bearer mt_pat_xxx"}}}}
Amazon Q Developer CLI (agent configuration file), then run /mcp in a session and open the sign-in link it prints:
{"mcpServers": {"mailtea": {"type": "http", "url": "https://api.mailtea.app/mcp"}}}
Send one email. Replace the bracketed details with your own:
Send an email from [my verified sender] to [recipient]. Subject: [subject]. Message: [body].
Schedule a send:
Schedule this email for [date and time, including time zone]. Use [verified sender] and send only to [recipient].
Check delivery:
Check my recent Mailtea emails and explain any failed deliveries.
Create a newsletter draft:
Draft a newsletter for [publication] about [topic]. Give it a clear subject and one call to action. Do not send it yet.
Design your website:
Draft a home page for [publication] using its brand and existing content. Do not publish it yet.
| What you see | What to do |
|---|---|
| No Mailtea tools after installing | Open a new session, check that the plugin is enabled, and connect Mailtea. |
| No browser sign-in prompt | Reconnect from the terminal or MCP settings. See the table below. |
| No publication available | Create one in Mailtea, or reconnect with access to an existing publication. |
| No sender, or the domain is not verified | Follow domain setup, complete the DNS records, and choose a sender on that domain. |
| Permission denied | Reconnect and select access that permits the action. Ask a publication owner if that option is unavailable. |
| A send timed out | Ask your agent to check recent emails before trying again, to avoid duplicates. |
| You want to disconnect | Revoke the connection in Mailtea's API keys / connected agents screen, and disable the plugin in your client. |
| Client | How to reconnect |
|---|---|
| Codex | codex mcp login mailtea |
| Claude Code | /mcp, or claude mcp login mailtea |
| Cursor | MCP settings, then Mailtea, then reconnect |
| VS Code | MCP: Browse servers, then Mailtea |
| Kiro | MCP settings |
| Grok Build | /marketplace, or grok mcp login |
**The r
Nur der Anfang wird gezeigt; den Rest findest du im Repo