# MCP-server för Brew: e-postmarknadsföring för AI-agenter

Anslut ChatGPT, Claude, Cursor eller valfri AI-agent till Brew via MCP. Agenter skapar, skickar, automatiserar och analyserar varumärkesenliga mejl.

Kanonisk URL: https://brew.new/sv/mcp

## Vad det är

En MCP-server (Model Context Protocol) som ger AI-agenter tillgång till Brew. Anslut den i ChatGPT, Claude, Grok, Cursor, Codex eller valfri MCP-klient, så sköter din agent hela cykeln för e-postmarknadsföring, med samma varumärke och data som i appen.

## Det här kan din agent göra

- Generera och iterera på varumärkesenliga mejldesigner
- Skicka och schemalägga kampanjer och testutskick via verifierade domäner
- Bygga automatiseringar: koppla utlösare till flöden i flera steg, testa, publicera och skicka händelser
- Hantera kontakter, anpassade fält och sparade målgrupper (segment)
- Läsa av statistik för leveranser, öppningar, klick, studsar och automatiseringar
- Lägga till varumärkesenliga bilder och rendera förhandsvisningar i HTML

## Från idé till inkorg till insikt

1. Designa: `create_email` från en prompt, sedan `edit_email` för att iterera. Varje ändring versionshanteras.
2. Skicka eller schemalägg: `send_email` till en sparad målgrupp via en verifierad domän, nu eller vid en senare tidpunkt med `scheduledAt`.
3. Automatisera: koppla en utlösare till ett flöde med `save_automation`, testa och publicera, och anropa sedan `fire_trigger_event` från din app.
4. Mät och förfina: läs `get_email_analytics` för varje utskick och mottagarnas engagemang, segmentera sedan om och försök igen.

## Anslut

ChatGPT på webben använder ett plugin för Brew. ChatGPT för dator och Codex delar inställningar för MCP-servern. I andra klienter följer du konfigurationen nedan, autentiserar dig och anropar sedan get_brew_capabilities.

```
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**.

[Lägg till i Cursor](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.

### Alternativ med API-nyckel

Om din klient inte kan använda OAuth skapar du en nyckel under Inställningar → API och följer dess headerformat. Det här exemplet använder mcpServers och 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.

## Kombinera med ditt CRM

Brew är den AI-nativa ESP:n: det beständiga mejlminnet och utskicksinfrastrukturen för agenter. Kombinera Brew med en MCP för CRM eller databerikning (Clay, Attio med flera) för att berika kontakter, bygga smarta segment och skicka personaliserade mejl: berika → segmentera → designa → skicka → mät → segmentera om.

## Arbetsflöden

Servern har guidade promptar och ett upptäcktsverktyg (`get_brew_capabilities`), så att agenter kedjar ihop verktygen i rätt ordning: lansera en kampanj, bygga ett segment och skicka, konfigurera en automatisering, analysera resultat och personalisera med en MCP för CRM.

## Vanliga frågor

### Vad är MCP-servern för Brew?

Det är en MCP-server (Model Context Protocol) som ger AI-agenter tillgång till Brew. Anslut den i ChatGPT, Claude, Grok, Cursor, Codex eller valfri MCP-klient, så kan din agent generera och iterera på mejldesigner, skicka och schemalägga kampanjer, bygga automatiseringar, hantera kontakter och segment och läsa av statistik, med samma varumärke och data som i appen.

### Hur ansluter jag den?

ChatGPT på webben använder ett plugin för Brew. ChatGPT för dator och Codex delar inställningar för MCP-servern. I andra klienter följer du konfigurationen nedan, autentiserar dig och anropar sedan get_brew_capabilities. Använd https://brew.new/api/mcp och följ konfigurationsguiden för klienter på https://docs.brew.new/api-reference/mcp/connect-your-client. Klienter utan OAuth kan använda en API-nyckel från Inställningar → API.

### Kan jag kombinera den med andra MCP:er, som Clay eller Attio?

Ja, det är där den verkligen kommer till sin rätt. Brew är den AI-nativa ESP:n: mejlminnet och utskicksinfrastrukturen som din agent styr. Kombinera Brew med en MCP för CRM eller databerikning (Clay, Attio med flera) för att få rik kontext om kontakterna, bygga smarta segment och skicka mycket personaliserade mejl. Din agent får dem att arbeta tillsammans.

### Kan den lika mycket som appen?

Den täcker cykeln inom e-postmarknadsföring: skapa, iterera, skicka, schemalägga, automatisera, segmentera och analysera, inklusive optimering av utskickstid. Du kan registrera en domän och sedan publicera dess DNS-poster hos din DNS-leverantör. Kontaktuppdateringar via CSV gäller befintliga kontakter; nya kontakter lägger du till via importen i appen, en integration eller ditt registreringsflöde. Varumärkets logotyper och konfigurationen av domäner för transaktionella mejl hanterar du i Brew. Med en anslutning för hela organisationen kan en administratör dessutom extrahera ett nytt varumärke från dess webbplats.

Läs mer: https://brew.new/sv/mcp · Dokumentation: https://docs.brew.new/api-reference/mcp/overview