GoodSender MCP Server

Free consent-based emailing and interactive email template design tools

Local serverstdio

What is the GoodSender MCP server?

Free consent-based emailing and interactive email template design tools. That is what the goodsender mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

  • 🛡️ Local server
  • Email contents, custom templates, recipient groups and sender identities are stored only on your machine
  • ✉️ Send emails in plain text, HTML or Markdown to one or more recipients
  • ✅ Send consentless transactional emails using built-in templates (OTP, MFA, Order Completion, etc.)
  • 🤝 Automatic consent flow handling
  • Recipients added via MCP receive the consent email

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Double — click the goodsender.mcpb file to open it in your AI client
  • goodsender-mcp-data — /data

Getting it running

Installation goes through your MCP client rather than a global install: point it at ghcr.io/good-sender/mcp on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: GOODSENDER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. GoodSender's toolset — Double, goodsender-mcp-data — is a fair guide to whether it matches your workflow. It is maintained by good-sender; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Doubleclick the goodsender.mcpb file to open it in your AI client.
goodsender-mcp-data/data

How to install the GoodSender MCP server

{
      ...
      "mcpServers": {
        "GoodSender": {
          "command": "<path to the unzipped binaries>/goodsender-mcp-darwin-arm64",
          "env": {
            "GOODSENDER_API_KEY": "<Your API key>"
          }
        }
      }
      ...
    }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GOODSENDER_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use GoodSender to Double.
  • Use GoodSender to goodsender-mcp-data.

Frequently asked questions

It connects GoodSender to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Double, goodsender-mcp-data) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with GoodSender directly.