DSH Plugins Marketplace

DSH Plugins

Plugins

/

dsh-mailgun

b

dsh-mailgun

Manifest valid

Send email through the Mailgun HTTP API with per-message open and click tracking, and read the delivery and engagement events — for DeepSeek Harness.

UI (client)hasBundlePatch

dsh-mailgun

Mailgun HTTP API tools for DeepSeek Harness: send a message with per-message open and click tracking, read the delivery and engagement events, list the sending domains and read the domain counters.

This plugin is send-and-track only. Reading mailboxes is the job of the dsh-email plugin, which owns IMAP and SMTP. Mailgun has no mailbox server of its own, so there is nothing here to read — and the separation keeps a send-only sending service out of the account list that dsh-email manages.

Several Mailgun accounts

One Mailgun account is one API key and one sending domain, so the plugin holds a list of accounts rather than a single one. Add them on the harness Settings → Mailgun page: one row per account, each with a label, the sending domain, the region, the From address and the API key.

A saved account is an accordion item: the collapsed line carries the label, the sending domain and the badges, and the form opens when the line is clicked. Collapsed is the standard state, also for an account that was just added.

The Add Mailgun account form stays open after it saves, so a second account is one more click away instead of another trip through the button. Several accounts may carry the same label — each one still gets its own id, its own key and its own place in the list.

Where each piece lives:

WhatWhere
The account list (label, domain, region, From)~/.dsh/data/dsh-mailgun/accounts.json
Each account's API keythe credential store, as the record dsh-mailgun/<id>

The account list is this plugin's own file rather than a section of the harness settings document, on purpose: the harness settings API is the one part of DSH whose shape differs between host releases — one exposes a namespace-registration API (ctx.settings.register), another a per-entry form API (ctx.settings.update) — and a plugin bound to either breaks on the other. The API keys are in the credential store regardless, because that is where a secret belongs.

The key is write-only from the browser: the settings backend reports whether a key is stored, never its value, so the page never holds a key it did not just type. The account id is derived from the label (Bold & Digital → bold-digital), and it is the id the credential record is keyed by.

One account is the default; the agent sends from it unless a tool names another one.

Install

From the Plugin Manager's Discover tab, or directly from npm:

dsh plugin --profile web add dsh-mailgun

The package is also on npm as dsh-mailgun, so npm install dsh-mailgun works too. To run it straight from a checkout instead:

dsh plugin --profile desktop add "link:/path/to/dsh-mailgun"

From a checkout

The plugin can also be registered as a local bundle in a profile:

# ~/.dsh/profiles/desktop/package.json
"dependencies": {
  "dsh-mailgun": "link:/path/to/dsh-mailgun"
},
"dsh": { "profile": { "bundles": [ ..., "dsh-mailgun" ] } }

Then link it into the profile:

cd ~/.dsh/profiles/desktop && pnpm install

Configure

The bundle patch carries only the fallbacks for an install that keeps one account in the patch rather than on the settings page:

- insert:
    - id: mailgun
      name: 'dsh-mailgun'
      config:
        domain: ''            # fallback sending domain
        region: us            # us | eu
        from: ''              # fallback From address
        apiKeyRef: MAILGUN_API_KEY

A single-account install may also read its key from the plugin-level reference instead of the settings page:

# ~/.dsh/.credentials.yaml
refs:
  MAILGUN_API_KEY: "key-..."

Tools

ToolWhat it does
mailgun_sendSend one message. o:tracking, o:tracking-opens and o:tracking-clicks are set on the send itself, so the dashboard toggle does not matter. Returns the Mailgun message id.
mailgun_eventsThe event feed: delivered, opened, clicked, failed, complained, unsubscribed. Filter by event name and recipient.
mailgun_domainsThe sending domains on the account with their state.
mailgun_statsThe aggregate counters for the domain: sent, delivered, opened, clicked, failed.

Every tool takes an optional account (id or label) to choose which configured Mailgun account to use; it defaults to the default account.

mailgun_send takes to, subject, text or html, plus optional cc, bcc, from, domain, tag, tracking (default true) and testMode (validate without delivering).

Why the HTTP API rather than SMTP

Over plain SMTP, Mailgun cannot set the per-message tracking flags — the o:tracking* options exist only on the HTTP API's POST /v3/{domain}/messages call. SMTP sends therefore arrive with no open or click tracking at all, and the dashboard-side tracking endpoints do not help either. The HTTP API is the only path that gives you both the send and its engagement counters.

This is also why the plugin does not reuse dsh-email for Mailgun: that plugin requires every account to carry an IMAP endpoint, which a send-only sending service does not have.

Notes

  • The API base is https://api.mailgun.net/v3 for the us region and https://api.eu.mailgun.net/v3 for eu. The region is per account.
  • The key and the sending domain must belong to the same Mailgun account.
  • Tracking flags per message: o:tracking=yes, o:tracking-opens=yes, o:tracking-clicks=htmlonly.
  • The raw web route /_dsh/dsh-mailgun/settings is localhost-only, because it carries API keys. The browser half uses the connection channel route /api/dsh-mailgun/settings instead.
  • The plugin depends on no harness settings service, so it loads on every host release.
  • The plugin's own icon is assets/icon.svg, exported as ./icon and read by the Plugin Manager for the plugin row. The settings navigation uses the same artwork, so the row and the section show one mark.
  • The section's visible strings go through the Client locale service under the dsh-mailgun.settings namespace, in English and Chinese.

Test

cd dsh-mailgun && npm test

The test loads the browser bundle the way the browser does and checks that apply registers both the settings.section and the settings.section.icon contribution. A React hook called from apply throws there ("Invalid hook call") and the settings section disappears without any error in the page — the test is what catches it.

Comments

Loading…

Similar plugins

dsh-agentmail

by zt8989

Agent Mail for DeepSeek Harness: send/receive email via agently-cli with session/thread routing

Tools & CapabilitiesManifest valid

★ 0

JavaScript

Nov 6, 2026

dsh plugin --profile web add @zt8989/dsh-agentmail

by Vergil-long

DeepSeek Harness 邮件通知插件:任务完成 / 工具等你授权 / 助手在等你回答时发邮件给你,配一个「离开模式」开关。设置全部集成在 harness 设置界面里。

Tools & CapabilitiesNotifications & IntegrationsManifest valid

★ 1

MIT

JavaScript

Sep 13, 2026

dsh plugin --profile web add dsh-email-notify

by Xixixiao2007

把每轮回答压成一条详略得当的摘要发到邮箱,并支持邮件回信作答或续接对话(DeepSeek Harness 插件)

Manifest valid

★ 0

MIT

JavaScript

Oct 5, 2026

dsh plugin --profile web add dsh-mail-digest

by STARDUSTLC666

DeepSeek Harness 邮件插件:IMAP/SMTP 收发、搜索、回复转发、邮件整理与增量收件,支持多邮箱预设、发信审批及 Web 设置与新邮件通知。

Tools & CapabilitiesManifest valid

★ 47

↓ 3.5k/wk

MIT

JavaScript

Nov 17, 2026

dsh plugin --profile web add dsh-email

by Yaya716

Persistent user-message tools for DeepSeek Harness Web: hover actions on user bubbles in the chat flow (copy, and edit-and-resend as a new message).

Manifest valid

★ 0

JavaScript

Aug 15, 2026

dsh plugin --profile web add @local/dsh-msg-tools

by GengDaPeng

Cross-session agent messaging for DeepSeek Harness with session discovery, offline delivery, delivery receipts, and sender-session navigation.

Tools & CapabilitiesManifest valid

★ 6

↓ 241/wk

MIT

JavaScript

Sep 15, 2026

dsh plugin --profile web add dsh-agent-message