Verwalte Abonnenten, Broadcasts, Sequenzen, Automatisierungen und Reporting direkt in der Mailrith Email-Marketing-Plattform.
Auch bekannt als anrawool/mailrith-agent-platform, mailrith, @mailrith/mcp-server
- Stars
- 0
- Tools
- —
- Downloads, 30 Tage
- 771
- Neueste Version
- 2.0.1
- Letzter Commit
- 11. Nov. 2026
- Lizenz
- MIT
Was ist Mailrith MCP?
Verwalte Abonnenten, Broadcasts, Sequenzen, Automatisierungen und Reporting direkt in der Mailrith Email-Marketing-Plattform.
Zusammenfassung generiert aus dem README des Projekts
Über Mailrith MCP server
Mailrith Email Marketing bietet eine Schnittstelle zur Verwaltung von Email-Marketing-Abläufen über einen MCP server. Entwickler und Nutzer können mit Abonnenten, Broadcasts, Sequenzen und Automatisierungen interagieren. Der Server unterstützt sowohl Remote-Verbindungen über einen gehosteten Endpoint unter api.mailrith.com/mcp als auch lokale Installationen via stdio oder self-hosted HTTP Transports. Remote-Clients wie Claude Desktop verbinden sich über Mailrith OAuth, während lokale stdio-Setups einen Workspace API Key benötigen, der über die Umgebungsvariable MAILRITH_API_KEY bereitgestellt wird.
Dieser Server bietet verschiedene Kompatibilitätsprofile, darunter submitted, compact und custom. Das submitted Profil ist für allgemeine Agenten konzipiert und enthält Tools wie subscribers_list, broadcasts_create und broadcasts_schedule. Es erzwingt strikte Permission-Checks basierend auf den gewährten OAuth Scopes oder dem Workspace API Key des Nutzers. Das System gewährleistet Sicherheit, indem sensible Webhook-Tokens beim Auslesen von Automatisierungen unkenntlich gemacht werden und Credentials abgelehnt werden, wenn sie als Command-Argumente übergeben werden, um eine Offenlegung in der Shell-Historie zu verhindern.
Was du damit machen kannst
- 1Email-Abonnentenlisten verwaltenLass die KI deine aktuelle Liste von E-Mail-Abonnenten abrufen oder anzeigen.
- 2Marketing-Broadcasts planenAnweise den Agenten, einen neuen E-Mail-Broadcast vorzubereiten und für einen bestimmten Zeitpunkt zu planen.
- 3Automatisierungs-Status aktualisierenNutze den Client, um den Status bestehender E-Mail-Automatisierungen oder Sequenzen zu ändern.
- 4Preflight-Checks für Broadcasts durchführenVerwende den Agenten, um einen Broadcast zu validieren, bevor er offiziell an die Empfänger versendet wird.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Mailrith MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenMailrith MCP in Claude Code installieren
$ claude mcp add --env 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' mailrith -- npx -y @mailrith/mcp-serverMailrith MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Mailrith MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"mailrith": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Mailrith MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"mailrith","type":"stdio","command":"npx","args":["-y","@mailrith/mcp-server"],"env":{"MAILRITH_API_KEY":"<YOUR_MAILRITH_API_KEY>"}}'Mailrith MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Mailrith MCP in Codex installieren
$ codex mcp add mailrith --env 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' -- npx -y @mailrith/mcp-serverMailrith MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.mailrith] command = "npx" args = ["-y", "@mailrith/mcp-server"] [mcp_servers.mailrith.env] MAILRITH_API_KEY = "<YOUR_MAILRITH_API_KEY>"
Mailrith MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' mailrith npx -- -y @mailrith/mcp-serverMailrith MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Konfiguration
MAILRITH_API_KEYErforderlichSecretA Mailrith workspace API key.
| Name | Beschreibung | Typ |
|---|---|---|
| MAILRITH_API_KEY | A Mailrith workspace API key. | ErforderlichSecret |
Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbaranrawool/mailrith-agent-platform is public and reachablegithub.com/anrawool/mailrith-agent-platform ↗Bestanden
- Paket nennt dieses Repository als Quelle@mailrith/mcp-server names anrawool/mailrith-agent-platform as sourcenpmjs.com/package/@mailrith/mcp-server ↗Bestanden
- Build-Provenienz (Sigstore-Attestierung)Sigstore attestation for @mailrith/mcp-servernpmjs.com/package/@mailrith/mcp-server/v/2.0.1#provenance ↗Bestanden
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-11-11github.com/anrawool/mailrith-agent-platform ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNo popular package one edit away from @mailrith/mcp-serverBestanden
- Keine kritischen Advisories im Paket oder seinen Abhängigkeiten101 resolved dependencies checked; no critical advisoryosv.dev ↗Bestanden
- Keine versteckten Anweisungen an das Modell0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-Handshakeinitialize answered with protocol 2025-06-18 in 98 msBestanden
README
Auf GitHub ansehenMailrith MCP Server
Official MCP server for Mailrith.
The server uses the stable @modelcontextprotocol/sdk package for hosted and
stdio transports while preserving Mailrith's generated operation schemas.
Use the remote MCP endpoint at https://api.mailrith.com/mcp for hosted agent
integrations, or run the local server from this repo for stdio or self-hosted HTTP use.
Claude Desktop and other user-connected remote MCP clients authenticate through
Mailrith OAuth. Code-first clients that can safely store credentials may send a
workspace API key or OAuth access token as Authorization: Bearer <credential>.
Official MCP Registry
The registry metadata in server.json identifies the server as
com.mailrith/mailrith. Clients can use the canonical Streamable HTTP endpoint
at https://api.mailrith.com/mcp, which authenticates through OAuth, or install
the local stdio package from npm. Local installs require a workspace API key in
MAILRITH_API_KEY.
The hosted server requests Full Email Marketing Access by default for a
general-purpose agent. It covers every public email-marketing operation in the
selected workspace, but not billing, team, account-security,
credential-reading, or internal administration. The
discovery_get_capabilities connection check requests the complete public
permission catalog so Mailrith can show every Work Profile and default to Full
Email Marketing Access. The user can choose Reporting, another focused Work
Profile, or custom permissions instead. OAuth stores only the permissions the
user approves, and every tool checks those permissions again when it runs.
MAILRITH_API_KEY="<secret>" pnpm --filter @mailrith/mcp-server exec tsx src/cli.ts --transport stdio
Local stdio reads MAILRITH_API_KEY from the client secret environment. The
server rejects credentials passed as command arguments so they do not appear in
process listings or shell history. Local stdio stops with a clear setup error
when the environment variable is missing because it has no browser-based OAuth
flow.
Self-hosted HTTP does not read a process-wide API key. Each client must send its
own workspace API key or OAuth access token in the Authorization header. The
built-in HTTP listener accepts only 127.0.0.1 or localhost; put a TLS reverse
proxy in front of it when another machine needs access.
The default submitted profile exposes a fixed reviewed catalog of focused
tools such as:
subscribers_listbroadcasts_createbroadcasts_preflightbroadcasts_schedulebroadcasts_sendsequences_update_statusautomations_update_status
Every submitted tool has a human-readable top-level title and
annotations.title, a narrow description, exact input and output schemas,
explicit safety annotations, and machine-readable operation permissions.
Request-body inputs expose their JSON type directly as well as their exact
referenced schema so connector review tools can validate them without expanding
$ref values first. Tools other than the connection check advertise their
exact OAuth permissions. The connection check advertises the complete
permission catalog so OAuth can offer every Work Profile; its result still
reports the exact permissions granted to the connection. The catalog stays the
same for every user so clients can review and select tools reliably. Workspace
role, plan, product readiness, and granted permissions are enforced when a tool
runs.
Anonymous clients may initialize and list this static catalog so ChatGPT and
other hosts can start OAuth linking. Anonymous tool calls never reach the
Mailrith product API and return HTTP 401 with a standards-based
WWW-Authenticate challenge instead. Authenticated calls that need more
permissions return HTTP 403 with the complete replacement permission set.
Single-tool responses also include MCP's tool-level OAuth challenge metadata
for clients that use it when linking or reconnecting an account.
Each anonymous HTTP request accepts one JSON-RPC message. Authenticated
requests may batch up to 25 messages. These limits keep discovery and tool
responses predictable for every connected workspace.
Automation reads never return saved webhook bearer tokens or custom header values. They return only whether each value is configured. If a client reads an Automation and sends the redacted definition back during an update, Mailrith preserves the existing values unless the client explicitly replaces or removes them. Changing the webhook destination requires new credential values so an old secret cannot be carried to another service.
The package also preserves two explicit compatibility profiles:
compactexposes the earlier seven discovery and routing tools.customexposes generated focused tools with caller-selected Work Profile, permission, and read-only filters.
Use these profiles only for local or purpose-built clients. The public ChatGPT/Codex plugin
and the Claude Connector use the fixed submitted profile at the single /mcp
endpoint.
Official Builds And Forks
Modified public versions must use distinct package, registry, plugin, and service names and clearly say that they are unofficial. See the Mailrith Trademark And Unofficial Fork Policy.
Mailrith MCP Fragen
Wie füge ich Mailrith MCP zu Claude Code hinzu?
Führe claude mcp add --env 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' mailrith -- npx -y @mailrith/mcp-server in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Mailrith MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Wie authentifiziere ich mich beim Mailrith MCP server?
Claude Desktop und andere Remote-Clients nutzen Mailrith OAuth, während Code-first-Clients einen Workspace API Key oder einen OAuth Access Token im Authorization Header verwenden können.
Welche Tools sind im Standardprofil verfügbar?
Das Standardprofil 'submitted' enthält Tools zum Verwalten von Abonnenten, zum Erstellen und Planen von Broadcasts sowie zum Aktualisieren des Status von Sequenzen und Automatisierungen.