---
title: "Mailgun Connector | Tajo"
description: "Tajo does not run a Mailgun connector today. Early code exists; this page lists what it does and what is planned."
url: https://tajo.io/docs/connectors/marketing/mailgun/
markdown: https://tajo.io/docs/connectors/marketing/mailgun.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
robots: noindex
---

# Mailgun Connector

[Set Noa](https://tajo.io/set-noa/)

Connector status: Planned Not built yet. Tajo does not run this connector today.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

Tajo does not run a Mailgun connector today. Early code exists, but it has not been run against a live Mailgun account and syncs nothing yet.

## What exists so far

- Reads mailing lists, their members, and the account’s event logs: deliveries, opens and clicks.

## Planned, not built

- Bounces and complaints as suppressions
- Engagement metrics as contact attributes
- Domain reputation monitoring

## Open-Source Implementation Map

This section is derived from official or public repository material discovered for the Mailgun connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.

### Repository Snapshot

| Repository | Commit | Languages / formats | Files |
| --- | --- | --- | --- |
| [mailgun/mailgun-mcp-server](https://github.com/mailgun/mailgun-mcp-server) | 3495e24 | TypeScript (10), JSON (5), Markdown (4), YAML (1), gitignore (1), npmignore (1) | 26 |

### Integration Shape

```mermaid
graph LR
  Source["Mailgun API / repository"] --> Auth["Auth and scopes"]
  Source --> Objects["Objects, events, and schemas"]
  Auth --> Tajo["Tajo connector runtime"]
  Objects --> Tajo
  Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"]
  Tajo --> Ops["Backfill, cursor, retries, logs"]
```

### What To Reuse

- Mailgun MCP Server
- Overview
- Capabilities
- - **Messaging** — Send emails, retrieve stored messages, resend messages
- - **Domains** — View domain details, verify DNS configuration, manage tracking settings (click, open, unsubscribe)

### Tajo Revamp Checklist

- Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
- Map primary resources into explicit Tajo sync objects with stable external IDs.
- Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
- Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
- Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
- Keep examples small and runnable against sandbox or test-mode accounts.

### Sources

- [mailgun/mailgun-mcp-server](https://github.com/mailgun/mailgun-mcp-server)
- [Vendor documentation](https://documentation.mailgun.com/docs/mailgun/mcp)