Mailing Engineer

com.mailing-engineerPublished by mailing-engineer.comOfficial publisherv2.0.0Updated Oct 26, 2026

E-Commerce Email Marketing, AI Newsletter Studio, DNS Audit & AWS SES Deliverability MCP.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for e-commerce email marketing, AI newsletter creation, DNS audits and AWS SES deliverability checks.

What you can do
  • The registry lists no individual tools, so capabilities come from the description only.
  • It is positioned as an e-commerce email marketing service reachable through MCP.
  • It advertises an AI newsletter studio for producing email campaigns.
  • It covers DNS audits and AWS SES deliverability work, suggesting checks on sending setup and inbox placement.
When to use it
Consider it if you run e-commerce email campaigns and want an assistant to help draft newsletters or check sending setup and deliverability through one hosted service.
Requirements
A remote streamable HTTP endpoint at mailing-engineer.com; no local package or environment variables are declared. OAuth authentication is required, so an account with the provider is needed.
Before you install
OAuth access to a marketing account may let the assistant read or change campaigns and sending configuration; confirm what scopes are granted. DNS and SES deliverability features may touch domain records or AWS sending settings, and campaign content may be sent to third parties.

Installation

In SourceWeft

  1. Open Mailing Engineer in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.mailing-engineer%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mailing-engineer": {
      "type": "http",
      "url": "https://mailing-engineer.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestOct 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.