Free consent-based emailing, blog publishing, and interactive email template design tools
From: header) and reference them by name.Grab the goodsender.mcpb file from the latest release.
Double-click the goodsender.mcpb file to open it in your AI client.
Note: Not every AI client supports MCP bundles or local MCP servers yet. Use a different installation method if nothing happens on double-click.
Run via
docker run -d -e GOODSENDER_API_KEY=<Your API Key> -v goodsender-mcp-data:/data ghcr.io/good-sender/mcp:latest
If your goal is to run the agent using this MCP fully autonomously, set GOODSENDER_DISABLE_ACTION_GUARDS=true to skip all action confirmations completely. See Action confirmation.
or add to docker-compose.yaml on your home server
services:
goodsender-mcp:
image: ghcr.io/good-sender/mcp:latest
ports:
- "9889:9889"
environment:
GOODSENDER_API_KEY: <Your API Key>
# GOODSENDER_DISABLE_ACTION_GUARDS: "true" # skip all action confirmations
volumes:
- goodsender-mcp-data:/data
restart: unless-stopped
volumes:
goodsender-mcp-data:
and run via
docker compose up -d
Grab the binaries.zip file from the latest release (includes MCP goodsender-mcp-* and CLI goodsender-* binaries).
Unzip it somewhere you can easily reference.
Modify your AI client config file, adding the MCP server configuration (example for Claude Desktop and Cursor on macOS):
{
...
"mcpServers": {
"GoodSender": {
"command": "<path to the unzipped binaries>/goodsender-mcp-darwin-arm64",
"env": {
"GOODSENDER_API_KEY": "<Your API key>"
}
}
}
...
}
For other platforms you must reference a corresponding binary instead of
darwin(macOS)
If your goal is to run the agent using this MCP fully autonomously, set GOODSENDER_DISABLE_ACTION_GUARDS=true to skip all action confirmations completely. See Action confirmation.
By default, mutating tools (create, publish, send, and similar) do not run immediately. They return a confirmation token. The agent must call confirm_action after you approve.
Set GOODSENDER_DISABLE_ACTION_GUARDS=true in the MCP server environment to skip that step. Tools then run when the client calls them. Use this for unattended loops (Cowork schedules, CI). Leave it unset if you want every send and publish to wait for your approval in the chat.
ℹ️ This will:
- Create/update the recipients in the database
- Add them to the "AI newsletter subscribers" recipient group, creating it if needed
ℹ️ This will:
- Create a draft email template in GoodSender format following best practices for email template creation
- Display interactive preview of this template draft (if AI client supports it)
ℹ️ Done during the template draft creation/editing, this will:
- Modify the template accordingly
- Display interactive preview of this template draft (if AI client supports it)
ℹ️ Done during the template draft creation/editing, this will:
- Send an email with mocked data generated from the current template draft only to you
ℹ️ Done during the template draft creation/editing, this will:
- Convert the current template draft to a persistent template stored in the local database
- Allow sending emails just by mentioning the template name
ℹ️ This will:
- Create and enqueue a a personalized template-based email for each recipient in the AI newsletter subscribers group
- For all recipients who haven't received an email with consent request, will request their consent for receiving emails from you
- Send emails to all recipients who granted their email consent
- Monitor all recipients with pending consent and send the email as soon as they grant it
ℹ️ This will:
- Create a draft post from the title and body
- Show a signed preview URL
- Publish the post
- Broadcast it to the group (consent flow still applies)
Telemetry is enabled by default. MCP server sends aggregate usage and reliability metrics to GoodSender to help improve the product.
Typical signals include:
We do not intentionally collect email bodies, recipient addresses, or template contents as part of this telemetry.
You can opt out of telemetry collection by setting GOODSENDER_TELEMETRY=false in the MCP server environment.
See the GoodSender Privacy Policy for how personal data is handled by the service.
This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.
https://github.com/good-sender/mcp/releases/download/v0.5.2/goodsender.mcpbotherGoodSender works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.