# Brew MCP 서버: AI 에이전트를 위한 이메일 마케팅

ChatGPT, Claude, Cursor 등 어떤 AI 에이전트든 MCP로 Brew에 연결하세요. 에이전트가 브랜드에 맞는 이메일을 생성하고, 보내고, 자동화하고, 분석해요.

정식 URL: https://brew.new/ko/mcp

## MCP 서버란

AI 에이전트가 Brew를 쓸 수 있게 해 주는 MCP(Model Context Protocol) 서버예요. ChatGPT, Claude, Grok, Cursor, Codex 등 어떤 MCP 클라이언트에서든 연결하면, 에이전트가 Brew 앱과 같은 브랜드와 데이터를 바탕으로 이메일 마케팅의 전 과정을 실행해요.

## 에이전트가 할 수 있는 일

- 브랜드에 맞는 이메일 디자인 생성 및 수정
- 인증된 도메인으로 캠페인과 테스트 발송을 보내고 예약
- 자동화 구축: 트리거를 다단계 플로우에 연결하고, 테스트하고, 게시하고, 이벤트 보내기
- 연락처, 사용자 지정 필드, 저장된 오디언스(세그먼트) 관리
- 전달, 오픈, 클릭, 반송, 자동화 분석 확인
- 브랜드에 맞는 이미지 추가 및 HTML 미리보기 렌더링

## 아이디어에서 받은편지함, 그리고 인사이트까지

1. 디자인: 프롬프트로 `create_email` 도구를 호출하고, `edit_email` 도구로 다듬으세요. 모든 변경 사항은 버전으로 남아요.
2. 발송 또는 예약: `send_email` 도구로 인증된 도메인을 통해 저장된 오디언스에게 지금 보내거나, `scheduledAt`에 미래 시각을 지정해 예약하세요.
3. 자동화: `save_automation` 도구로 트리거를 플로우에 연결하고, 테스트하고, 게시한 다음 앱에서 `fire_trigger_event` 도구를 호출하세요.
4. 측정 및 개선: `get_email_analytics` 도구로 발송별 성과와 수신자 참여를 확인한 다음, 세그먼트를 다시 나눠 다시 시도하세요.

## 연결

ChatGPT 웹에서는 Brew 플러그인을 사용해요. ChatGPT 데스크톱과 Codex는 MCP 서버 설정을 공유해요. 다른 클라이언트에서는 아래 설정을 따라 인증한 다음 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**.

[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.

### API 키 방식

클라이언트에서 OAuth를 쓸 수 없다면 설정 → API에서 키를 만들고 그 헤더 형식을 따르세요. 이 예시는 mcpServers 키와 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.

## CRM과 함께 쓰기

Brew는 AI 네이티브 ESP로, 에이전트를 위한 지속적인 이메일 메모리이자 발송 인프라예요. CRM이나 데이터 보강 MCP(Clay, Attio 등)와 함께 쓰면 연락처를 보강하고, 똑똑한 세그먼트를 만들고, 개인화된 이메일을 보낼 수 있어요: 보강 → 세그먼트 → 디자인 → 발송 → 측정 → 재세그먼트.

## 워크플로

서버에는 가이드 프롬프트와 탐색 도구(`get_brew_capabilities`)가 들어 있어서 에이전트가 올바른 순서로 도구를 이어 써요: 캠페인 시작, 세그먼트 생성 및 발송, 자동화 설정, 성과 분석, CRM MCP를 활용한 개인화.

## 자주 묻는 질문

### Brew MCP 서버란 무엇인가요?

AI 에이전트가 Brew를 쓸 수 있게 해 주는 MCP(Model Context Protocol) 서버예요. ChatGPT, Claude, Grok, Cursor, Codex 등 어떤 MCP 클라이언트에서든 연결하면, 에이전트가 Brew 앱과 같은 브랜드와 데이터로 이메일 디자인을 생성하고 다듬고, 캠페인을 보내고 예약하고, 자동화를 만들고, 연락처와 세그먼트를 관리하고, 성과 분석을 확인할 수 있어요.

### MCP 서버는 어떻게 연결하나요?

ChatGPT 웹에서는 Brew 플러그인을 사용해요. ChatGPT 데스크톱과 Codex는 MCP 서버 설정을 공유해요. 다른 클라이언트에서는 아래 설정을 따라 인증한 다음 get_brew_capabilities 도구를 호출하세요. 서버 URL: https://brew.new/api/mcp. 클라이언트별 설정 가이드는 https://docs.brew.new/api-reference/mcp/connect-your-client에서 확인하세요. OAuth를 지원하지 않는 클라이언트는 설정 → API에서 발급한 API 키를 쓸 수 있어요.

### Clay나 Attio 같은 다른 MCP와 함께 쓸 수 있나요?

네. 바로 그럴 때 진가를 발휘해요. Brew는 AI 네이티브 ESP로, 에이전트가 운영하는 이메일 메모리이자 발송 인프라예요. CRM이나 데이터 보강 MCP(Clay, Attio 등)와 함께 쓰면 풍부한 연락처 맥락을 더하고, 똑똑한 세그먼트를 만들고, 고도로 개인화된 이메일을 보낼 수 있어요. 에이전트가 두 서버를 함께 조합해 써요.

### MCP 서버도 앱만큼 강력한가요?

생성, 수정, 발송, 예약, 자동화, 세그먼트, 분석으로 이어지는 이메일 마케팅 사이클을 다루며, 발송 시간 최적화도 포함돼요. 도메인을 추가한 다음, 사용하는 DNS 제공업체에서 해당 DNS 레코드를 등록할 수 있어요. CSV로 하는 연락처 업데이트는 기존 연락처에 적용돼요. 새 연락처는 앱 내 가져오기, 연동, 또는 회원가입 과정으로 추가하세요. 브랜드 로고와 트랜잭션 도메인 설정은 Brew에서 관리하세요. 조직 단위로 연결하면 관리자가 웹사이트에서 새 브랜드를 추출할 수도 있어요.

더 알아보기: https://brew.new/ko/mcp · 문서: https://docs.brew.new/api-reference/mcp/overview