# Brew-MCP-Server: E-Mail-Marketing für KI-Agenten

Verbinde ChatGPT, Claude, Cursor oder jeden KI-Agenten per MCP mit Brew. Agenten erstellen, versenden, automatisieren und analysieren markenkonforme E-Mails.

Kanonische URL: https://brew.new/de/mcp

## Was ist das?

Ein MCP-Server (Model Context Protocol), über den KI-Agenten auf Brew zugreifen. Verbinde ihn in ChatGPT, Claude, Grok, Cursor, Codex oder einem beliebigen MCP-Client, und dein Agent steuert den kompletten E-Mail-Marketing-Zyklus – mit derselben Marke und denselben Daten wie die Brew-App.

## Was dein Agent kann

- Markenkonforme E-Mail-Designs generieren und weiterentwickeln
- Kampagnen und Testversände über verifizierte Domains versenden und planen
- Automatisierungen erstellen: Trigger mit mehrstufigen Flows verknüpfen, testen, veröffentlichen und Events auslösen
- Kontakte, benutzerdefinierte Felder und gespeicherte Zielgruppen (Segmente) verwalten
- Analysen zu Zustellung, Öffnungen, Klicks, Bounces und Automatisierungen abrufen
- Markenkonforme Bilder hinzufügen und HTML-Vorschauen rendern

## Von der Idee über den Posteingang bis zur Erkenntnis

1. Gestalten: `create_email` aus einem Prompt, dann `edit_email` zum Iterieren. Jede Änderung wird versioniert.
2. Senden oder planen: `send_email` an eine gespeicherte Zielgruppe über eine verifizierte Domain – sofort oder zu einem späteren Zeitpunkt über `scheduledAt`.
3. Automatisieren: Verknüpfe mit `save_automation` einen Trigger mit einem Flow, teste und veröffentliche ihn und ruf dann `fire_trigger_event` aus deiner App auf.
4. Messen & verbessern: Lies mit `get_email_analytics` die Daten jedes Versands und das Engagement seiner Empfänger aus, segmentiere dann neu und versuch es noch einmal.

## Verbinden

ChatGPT im Web nutzt ein Brew-Plugin. ChatGPT Desktop und Codex teilen sich die MCP-Server-Einstellungen. Folge in anderen Clients der Einrichtung unten, authentifiziere dich und ruf dann get_brew_capabilities auf.

```
https://brew.new/api/mcp
```

### Claude Desktop

#### Custom connector

1. Open **Customize → Connectors → + Add → Add custom connector**.
2. Name it Brew, enter the server URL below, and select **Continue**. Review the detected authentication settings and continue.

```text
https://brew.new/api/mcp
```

Choose **Sign in now** or connect when needed. Finish adding the connector, select **Connect**, sign in with Brew, and choose one brand or all brands.

Enable Brew from the conversation’s **+ → Connectors** menu. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

For Team or Enterprise, an owner or authorized admin first uses **Organization settings → Connectors → Add → Custom → Web**. Members then connect individually. Free accounts are limited to one custom connector.

#### API-key alternative

1. Use the same custom connector flow and server URL. Choose **No sign in** when using a fixed API key.

```text
https://brew.new/api/mcp
```

Under **Request headers**, add **Authorization** with the value **Bearer brew_YOUR_API_KEY**, using a key from Brew’s **Settings → API**. Finish adding the connector.

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

On Team or Enterprise, a fixed credential is shared by everyone using the connector. Choose a key limited to the access those members need.

### ChatGPT web

1. On chatgpt.com, open **Plugins → + → Add custom MCP server**.
2. Name it Brew. Under **Connection**, enter the server URL below and choose **OAuth**.
3. Review the warning, select **I understand and want to continue**, then **Create as a plugin**.

```text
https://brew.new/api/mcp
```

Install the plugin. Complete the OAuth sign-in with Brew, choose one brand or all brands, and approve the access when prompted.

In a new chat, type **@** and select **Brew**. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Full MCP support on the web requires Business or Enterprise/Edu. Pro supports read/fetch access. Workspace permissions govern who can create custom MCP plugins; Business requires an admin or owner.

If tools changed after installation, refresh the plugin’s tools or actions using the controls your workspace provides. An administrator may need to review and publish the update.

### Grok

#### Web connector

1. Open **grok.com/connectors → New Connector → Custom** and enter the server URL below.

```text
https://brew.new/api/mcp
```

Start authentication, sign in with Brew, select a brand or all brands, and approve access.

Start a new chat; Grok can use connected tools when relevant. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

For Business or Enterprise, a team admin provisions the connector first.

#### Grok Build

1. Run the command below.

```bash
grok mcp add --transport http brew 'https://brew.new/api/mcp'
```

If authentication is needed, open **/mcps**, select Brew, and press **i** to sign in with Brew and select your brand.

Run `grok mcp doctor brew`, then start a session. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

### Claude Code

1. Run the command below with **--scope user** for every project, or omit it for this project’s local configuration. Adding the server only saves its configuration.

```bash
claude mcp add --transport http --scope user brew 'https://brew.new/api/mcp'
```

Run `claude mcp login brew`, or open **/mcp** in a Claude Code session and select Brew to authenticate. Sign in with Brew and choose a brand or all brands.

Run **/mcp** to confirm Brew is connected. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

### Cursor

1. Use **Add to Cursor** below, or merge the configuration into **~/.cursor/mcp.json** (all projects) or **.cursor/mcp.json** (this project).

```json mcp.json
{
  "mcpServers": {
    "brew": {
      "url": "https://brew.new/api/mcp"
    }
  }
}
```

Open **Customize → MCP**, select Brew, and use its sign-in action if prompted. Sign in with Brew and choose a brand or all brands.

Confirm Brew’s tools appear in Customize. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Older Cursor builds call this settings section **Tools & MCP**.

[Zu Cursor hinzufügen](cursor://anysphere.cursor-deeplink/mcp/install?name=brew&config=eyJ1cmwiOiJodHRwczovL2JyZXcubmV3L2FwaS9tY3AifQ)

### OpenCode

1. Merge this block into **~/.config/opencode/opencode.json**.

```json opencode.json
{
  "mcp": {
    "brew": {
      "type": "remote",
      "url": "https://brew.new/api/mcp",
      "enabled": true
    }
  }
}
```

Run `opencode mcp auth brew`, sign in with Brew, and select a brand or all brands. OpenCode can also prompt on first use.

Run `opencode mcp list` to confirm Brew is connected. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

### VS Code

1. Run **MCP: Add Server** from the Command Palette and choose HTTP, or create **.vscode/mcp.json** with the block below.
2. For all workspaces, use **MCP: Open User Configuration**.

```json mcp.json
{
  "servers": {
    "brew": {
      "type": "http",
      "url": "https://brew.new/api/mcp"
    }
  }
}
```

Select **Start** above Brew’s entry in mcp.json. Complete the browser sign-in with Brew and select a brand or all brands.

In Chat, select **Agent**, then **Configure Tools** and enable Brew’s tools. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Requires GitHub Copilot. On Copilot Business or Enterprise, an administrator must allow MCP servers in Copilot.

### Codex and ChatGPT desktop

#### ChatGPT desktop

1. Open **Settings → Plugins → MCPs → Add → Add MCP server**. Some builds use **Settings → MCP servers → Add server**.
2. Name it brew, select **Streamable HTTP**, and enter the URL below. Leave token and header fields empty for OAuth, then **Save**. Restart the connection if offered.

```text
https://brew.new/api/mcp
```

Select **Authenticate** on the Brew server, sign in with Brew, and choose a brand or all brands.

Type **/mcp** to inspect connected servers. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

#### Codex CLI or IDE configuration

1. Merge this block into **~/.codex/config.toml**. The desktop app, CLI and IDE extension share it on the same Codex host.

```toml config.toml
[mcp_servers.brew]
url = "https://brew.new/api/mcp"
```

Run `codex mcp login brew`, sign in with Brew, and select a brand or all brands. The desktop and IDE server lists also offer **Authenticate**.

Run `codex mcp list` or **/mcp** in a session. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Windows and WSL can use different hosts and home directories. ChatGPT web does not read this file. For an API key, set bearer_token_env_var to the name of an environment variable containing your Brew key.

### Manus

1. Open **Connectors → Create → Add MCP by URL**. Name the server Brew and enter the URL below. Older builds use **Settings → Integrations → Custom MCP Servers → Add Server**.

```text
https://brew.new/api/mcp
```

Create a key in Brew’s **Settings → API**. Use the key in Manus’s bearer-token field, or set **Authorization** to **Bearer brew_YOUR_API_KEY**. Save and test the connection.

Confirm Brew’s tools are available. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Use API-key authentication for custom servers. Brew OAuth in Manus’s custom-server flow still needs a live compatibility check.

### Devin Desktop

1. Merge this block into **~/.config/devin/mcp_config.json** on macOS/Linux, or **%APPDATA%\devin\mcp_config.json** on Windows. For private project settings, use **.devin/mcp_config.local.json**.

```json mcp_config.json
{
  "mcpServers": {
    "brew": {
      "url": "https://brew.new/api/mcp"
    }
  }
}
```

Run `devin mcp login brew` in Devin CLI, or use the authentication action when Devin Local first uses Brew. Sign in with Brew and select a brand or all brands.

Run `devin mcp list` or inspect the session’s MCP servers. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Current Devin Desktop uses Devin Local. Upgrade legacy Windsurf builds before following these steps. Organization policy may restrict available servers.

### Cline

#### Remote Servers

1. Click the **MCP Servers** icon and open **Remote Servers**.
2. Enter Server Name brew and the Server URL below. Choose **Streamable HTTP**, then **Add Server**.

```text
https://brew.new/api/mcp
```

Click **Authenticate** on the Brew server row. Complete the browser sign-in with Brew and select a brand or all brands.

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

#### JSON alternative

1. Open **MCP Servers → Configure → Configure MCP Servers** and merge the block below into the settings file. Save it.

```json cline_mcp_settings.json
{
  "mcpServers": {
    "brew": {
      "type": "streamableHttp",
      "url": "https://brew.new/api/mcp",
      "disabled": false
    }
  }
}
```

Click **Authenticate** on Brew’s server row, sign in with Brew, and select a brand or all brands.

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

The type field is required here: omitting it selects legacy SSE in Cline.

### Goose

1. Run goose configure. Choose **Add Extension → Remote Extension (Streamable HTTP)**, name it brew, and enter the endpoint below.

```bash
goose configure
# Add Extension → Remote Extension (Streamable HTTP)
# name: brew
# endpoint: https://brew.new/api/mcp
```

Complete the OAuth sign-in when Goose requests it. Sign in with Brew and select a brand or all brands.

Start a session with the Brew extension enabled. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Goose Desktop: open **Extensions → Add custom extension**, choose **Streamable HTTP**, and enter the same endpoint.

### Any MCP client

1. Use your client’s documented remote-server format. The example below is for clients that accept mcpServers with type http. Merge it into your existing config.

```json mcp.json
{
  "mcpServers": {
    "brew": {
      "type": "http",
      "url": "https://brew.new/api/mcp"
    }
  }
}
```

Run the client’s sign-in or authenticate action, then sign in with Brew and choose a brand or all brands. For clients without OAuth, use an API-key bearer header in their supported format.

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

This example is for clients that accept mcpServers and type: http. VS Code uses servers, OpenCode uses mcp and type: remote, and Cline requires type: streamableHttp. Follow your client’s recipe.

### Alternative mit API-Key

Wenn dein Client kein OAuth nutzen kann, erstelle unter Einstellungen → API einen Key und folge dem Header-Format deines Clients. Dieses Beispiel verwendet mcpServers und type: http:

```json
{
  "mcpServers": {
    "brew": {
      "type": "http",
      "url": "https://brew.new/api/mcp",
      "headers": {
        "Authorization": "Bearer brew_YOUR_API_KEY"
      }
    }
  }
}
```
This example is for clients that accept mcpServers and type: http. VS Code uses servers, OpenCode uses mcp and type: remote, and Cline requires type: streamableHttp. Follow your client’s recipe.

## Mit deinem CRM kombinieren

Brew ist der KI-native ESP: das dauerhafte E-Mail-Gedächtnis und die Versandinfrastruktur für Agenten. Kombiniere Brew mit einem CRM- oder Enrichment-MCP (Clay, Attio und andere), um Kontakte anzureichern, intelligente Segmente zu bilden und personalisierte E-Mails zu versenden: anreichern → segmentieren → gestalten → versenden → messen → neu segmentieren.

## Workflows

Der Server liefert geführte Prompts und ein Discovery-Tool (`get_brew_capabilities`) mit, damit Agenten die Tools in der richtigen Reihenfolge verketten: eine Kampagne starten, ein Segment bilden und versenden, eine Automatisierung einrichten, die Performance analysieren und mit einem CRM-MCP personalisieren.

## Häufig gestellte Fragen

### Was ist der Brew-MCP-Server?

Ein MCP-Server (Model Context Protocol), über den KI-Agenten auf Brew zugreifen. Verbinde ihn in ChatGPT, Claude, Grok, Cursor, Codex oder einem beliebigen MCP-Client, und dein Agent kann E-Mail-Designs generieren und weiterentwickeln, Kampagnen versenden und planen, Automatisierungen erstellen, Kontakte und Segmente verwalten und Performance-Analysen abrufen – mit derselben Marke und denselben Daten wie die Brew-App.

### Wie verbinde ich den Brew-MCP-Server?

ChatGPT im Web nutzt ein Brew-Plugin. ChatGPT Desktop und Codex teilen sich die MCP-Server-Einstellungen. Folge in anderen Clients der Einrichtung unten, authentifiziere dich und ruf dann get_brew_capabilities auf. Verwende https://brew.new/api/mcp und folge der Einrichtungsanleitung für deinen Client unter https://docs.brew.new/api-reference/mcp/connect-your-client. Clients ohne OAuth können einen API-Key aus Einstellungen → API verwenden.

### Kann ich Brew mit anderen MCPs wie Clay oder Attio kombinieren?

Ja – genau da spielt Brew seine Stärken aus. Brew ist der KI-native ESP: das E-Mail-Gedächtnis und die Versandinfrastruktur, die dein Agent bedient. Kombiniere Brew mit einem CRM- oder Enrichment-MCP (Clay, Attio und andere), um Kontakte mit reichhaltigem Kontext anzureichern, intelligente Segmente zu bilden und hochgradig personalisierte E-Mails zu versenden. Dein Agent bringt beide zusammen.

### Ist der MCP-Server so leistungsfähig wie die App?

Er deckt den E-Mail-Marketing-Zyklus ab: erstellen, iterieren, versenden, planen, automatisieren, segmentieren und analysieren – einschließlich der Versandzeitoptimierung. Du kannst eine Domain hinzufügen und ihre DNS-Einträge dann bei deinem DNS-Anbieter anlegen. Aktualisierungen per CSV gelten für bestehende Kontakte; neue Kontakte fügst du über den Import in der App, eine Integration oder deinen Registrierungsprozess hinzu. Markenlogos und die Einrichtung transaktionaler Domains verwaltest du in Brew. Über eine Verbindung für die ganze Organisation kann ein Admin außerdem eine neue Marke von ihrer Website auslesen.

Mehr erfahren: https://brew.new/de/mcp · Dokumentation: https://docs.brew.new/api-reference/mcp/overview