GoodSender

io.github.good-senderPublished by GitHub account good-senderv0.9.1Updated Nov 3, 2026

Publish blog posts, send newsletters and emails from Claude, Claude Code, Codex and ChatGPT.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & CollaborationBusiness & Commerce

Overview

GoodSender's hosted MCP server (mcp.goodsender.com); OAuth sign-in required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
mcp.goodsender.com
Last checked

Installation

In SourceWeft

  1. Open GoodSender 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/io.github.good-sender%2Fgoodsender-mcp/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": {
    "goodsender": {
      "type": "http",
      "url": "https://mcp.goodsender.com/"
    }
  }
}

README

GoodSender MCP Server

Publish blog posts, send newsletters and emails from Claude, Claude Code, Codex and ChatGPT. Send consent-based email and transactional email (OTP and MFA codes), and publish blog posts on your own domain. Connect to the hosted server with OAuth and nothing to install, or run it locally with an API key.

What you can do

Ask your assistant things like:

  • "Write a post about our new release, publish it on my blog and email it to subscribers."
  • "Draft a post from these notes and show me the preview before anything goes live."
  • "Connect blog.example.com to my blog and tell me which DNS records to add."
  • "Create a custom design for my blog that matches our logo, and show me a preview first."
  • "Send a password reset code to [email protected] with the OTP template."
  • "Email the March update to the beta-users group."

Posts are always created as drafts. Before publishing, the assistant shows where the post will go (your blog, the newsletter, connected social accounts) and asks you to approve it. See Action confirmation for how approval works on the hosted and local servers. The newsletter email carries the subject, the cover image when one is set, a summary and a link to the published post, not the full post body. Transactional templates such as OTP codes send right away. Other emails wait until the recipient consents. See Email sending.

Quick start (hosted, OAuth)

Hosted server URL:

https://mcp.goodsender.com/

You sign in to GoodSender in the browser the first time the client connects. To use blog tools, you need a GoodSender workspace with a blog. To send the optional newsletter, set up its sender identity and a public blog address first.

Claude Desktop

On Free, Pro or Max: open Customize → Connectors, choose Add → Add custom connector, and enter https://mcp.goodsender.com/. Keep the sign-in option so the OAuth flow runs the first time you use the connector.

On Team or Enterprise, an organization owner first adds GoodSender in Organization settings → Connectors → Add → Custom → Web. Members can connect it after that.

Claude Code

sh
claude mcp add --transport http goodsender https://mcp.goodsender.com/claude mcp login goodsender

Complete the OAuth flow in the browser. Check the connection with claude mcp get goodsender, or run /mcp in an interactive session.

Codex

sh
codex mcp add goodsender --url https://mcp.goodsender.com/codex mcp login goodsender

The Codex CLI and IDE extension share this configuration. The login command completes the browser flow.

ChatGPT

Turn on developer mode under Settings → Apps & Connectors → Advanced settings. Create an app with the server URL https://mcp.goodsender.com/ and OAuth authentication, then sign in to GoodSender when prompted. Pick the app from the + menu in a new chat.

Publishing needs MCP apps with write actions. OpenAI offers these as a beta on Business, Enterprise and Edu workspaces, and an admin may have to allow developer mode. Other plans may connect read-only. Menu names change between ChatGPT releases.

Gemini CLI

sh
gemini extensions install https://github.com/good-sender/mcp

The extension adds the hosted server. The browser sign-in (OAuth) opens the first time a tool runs; run /mcp auth goodsender in a session to sign in again. Gemini CLI is available to organisations on Gemini Code Assist Standard or Enterprise and through paid Gemini API keys. Individual Google AI accounts moved to Antigravity CLI on 2026-06-18; that CLI is not covered here.

Full guide: goodsender.com/docs/mcp.

Local install

The local server uses an API key. Create one on the API keys page of your GoodSender dashboard. Treat the key as a secret: never commit or share it.

MCP Bundle (`.mcpb` file, easiest)

  • 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.

Docker image / self-hosting

Run via

sh
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

yaml
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

bash
docker compose up -d
Manual configuration (JSON)

  • 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):

    json
    {  ...  "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.

Environment variables

VariableRequiredMeaning
GOODSENDER_API_KEYYesYour GoodSender API key.
GOODSENDER_DISABLE_ACTION_GUARDSNotrue makes mutating tools run without a confirmation step. See Action confirmation.
GOODSENDER_TELEMETRYNofalse opts out of usage and reliability telemetry. See Telemetry & privacy.

Action confirmation

Every tool declares whether it only reads, or changes something. Tools that publish, send, delete or change live state are marked destructive, so clients such as Claude ask you before running them.

  • Hosted server (mcp.goodsender.com): that client prompt is the approval step. Tools run when you approve the call, and confirm_action is not offered.
  • Local server: action guards add a second step by default. A tool that publishes, sends, deletes or changes the live blog design returns a confirmation token instead of acting, and confirm_action runs it once you approve. Set GOODSENDER_DISABLE_ACTION_GUARDS=true in the server environment to skip that step, for example for unattended loops (scheduled agents, CI).
  • CLI (the goodsender-* binaries in binaries.zip): runs with action guards off. A command you type is the approval, so it acts immediately and there is no confirm_action step.

Email sending

GoodSender sends email as well as blog posts. Permission protects deliverability, so cold outreach is not supported. Email tools work with the hosted server and with a local server.

  • 🤝 Consent handling. Recipients you add get a consent request by email. Custom emails to a recipient without consent wait in a queue. Emails to recipients who already consented go out right away.
  • 🔁 Consent flow. You do not track consent yourself. After a recipient consents, their queued emails go out when you ask to send pending emails (send_pending_emails) or use another tool that sends email. Nothing is sent while the server is idle.
  • ✅ Transactional templates. Built-in templates send right away, without a consent step: OTP code, MFA enrollment, new device login, password changed, email changed, order receipt and order completed.
  • ✉️ Formats. Send plain text, HTML or Markdown to one or more addresses, or to whole groups.
  • 📝 Custom templates. Create and edit templates with dynamic variables. Preview them in the chat with sample data, send a test email, then save and send by template name.
  • 👥 Recipient groups. Organize recipients into groups and address a whole group by name.
  • 🏷️ Sender identities. Manage From: identities on a verified domain and refer to them by name.
  • 📊 Health metrics. Check email health metrics for each sender domain.
  • 🛡️ Where data lives. Pending emails, custom templates, recipient groups and sender identities are stored in the MCP server's database: on your machine for a local server, on the server host for the hosted connection. Sending uses the GoodSender API. Blog posts, settings and designs are stored on GoodSender servers.
Example email prompts
Add 'John Doe <[email protected]>' and 'Jane Doe <[email protected]>' to the AI newsletter subscribers group

ℹ️ This will:

  • Create/update the recipients in the database
  • Add them to the "AI newsletter subscribers" recipient group, creating it if needed
Create a GoodSender template for a weekly AI news digest sent to the AI newsletter subscribers group

ℹ️ 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)
Increase the number of news in the digest to 5

ℹ️ 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)
Send a test email to me: 'Good Sender <[email protected]>'

ℹ️ Done during the template draft creation/editing, this will:

  • Send an email with mocked data generated from the current template draft only to you
Save the template as "Weekly AI news"

ℹ️ Done during the template draft creation/editing, this will:

  • Convert the current template draft to a persistent template stored in the MCP server's database
  • Allow sending emails just by mentioning the template name
Gather this week's AI news and send them using the "Weekly AI news" template

ℹ️ This will:

  • Create and enqueue 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
  • Keep the other emails queued; they go out after the recipient consents, when you send pending emails
[Example 1] [Example 2]

Tools

Blog and newsletter

ToolWhat it does
Posts and newsletter
list_postsList all posts, drafts and published, with the blog's byline and taxonomy.
get_postGet one post, including its markdown body.
create_postCreate a draft post. It never publishes or sends.
edit_postChange a draft or published post.
delete_postPermanently delete a post.
create_post_previewCreate a signed preview URL for a draft or published post.
upload_post_imageUpload an image (JPEG, PNG, GIF or WebP) for a post and get back its URL.
get_post_distributionShow where a post goes when published: the newsletter and the dev.to, X, LinkedIn, Bluesky and Mastodon destinations.
set_post_distributionChoose those destinations and review their text, newsletter subject and summary.
publish_postPublish the post to the public blog, then act on its distribution plan.
send_post_testSend a test email of the post to one inbox.
broadcast_postEmail a published post's newsletter to consented subscribers, at most once per post.
reannounce_postPost a published post to one announce destination (X, LinkedIn, Bluesky or Mastodon) again.
Blog settings and custom domain
get_blogGet blog settings (title, description, sender, theme, custom domain) and whether a custom design is live.
update_blogCreate or change blog settings, including SEO title and description.
connect_blog_domainClaim a custom hostname for the blog and get the DNS records to add.
get_blog_custom_domainCheck custom domain status and DNS targets.
remove_blog_custom_domainRemove the blog's custom domain.
Blog design
blog_design_template_formatDocumentation for the blog design template format.
blog_design_listList saved designs, flagging the active one and the stock one.
blog_design_createCreate a new design from templates and images.
blog_design_editEdit a design's templates.
blog_design_get_latest_checkpointGet the latest version of a design.
blog_design_checkpoint_listList the versions of a design.
blog_design_checkpoint_restoreGo back to an earlier version, deleting the newer ones.
blog_design_saveKeep a version and delete the older ones.
blog_design_activateMake a saved design the live design of the blog.
blog_design_image_upload_urlGet an upload URL for a logo or favicon.

Email

ToolWhat it does
Sending
enqueue_emailQueue an email in plain text, HTML or Markdown to addresses or groups. It is sent once the recipient consents.
enqueue_template_emailQueue a template-based email. It is sent once the recipient consents.
send_consentless_emailSend a built-in transactional template (OTP code, MFA enrollment, new device login, password or email changed, order receipt or completion) right away.
send_pending_emailsSend queued emails whose recipients have consented since they were queued.
send_template_draft_test_emailSend a test email from a template draft to one recipient.
Templates
template_formatDocumentation for the email template format.
create_template_draftStart a new template draft.
edit_templateEdit a template or draft with search-and-replace changes.
get_templateGet a saved template by name.
get_template_contentGet a template's current content, including unsaved edits.
render_template_previewRender a template preview with sample data.
save_templateSave a template draft.
list_templatesList email templates.
delete_templateDelete a template and the emails created from it.
Recipients and groups
create_recipientsAdd recipients and request their consent.
list_recipientsList recipients with group memberships and their last known consent status.
edit_recipientChange a recipient's display name.
delete_recipientsPermanently delete recipients and their emails.
create_groupCreate a recipient group.
list_groupsList recipient groups.
add_group_membersAdd recipients to a group.
remove_group_membersRemove recipients from a group.
Senders
create_sender_identityCreate a From: identity on a verified domain.
edit_sender_identityChange a sender identity's display name.
list_sender_identitiesList sender identities and whether each domain is verified.
check_sender_domain_statsShow email health metrics for each sender domain. Read-only.
Action confirmation (blog and email)
confirm_actionRun an action you approved, for both blog and email tools. Present only on a local server with action guards on (see Action confirmation).

FAQ

Is there a blog platform with an official MCP server? Yes. GoodSender publishes this server for its blog platform. Connect the hosted server at https://mcp.goodsender.com/ with OAuth, or run it locally. See the MCP connection guide.

How do I publish a blog post from Claude Code? Add the server with claude mcp add --transport http goodsender https://mcp.goodsender.com/ and sign in with claude mcp login goodsender. Then ask Claude Code to draft the post, show the preview and publish it. The MCP connection guide walks through your first publish.

Can Codex publish posts to my blog on my own domain? Yes. Connect Codex with codex mcp add goodsender --url https://mcp.goodsender.com/, then ask it to connect your domain. It returns the DNS records you add at your DNS provider, and published posts appear at that address. Setup steps are in the MCP connection guide.

Can it send the post as a newsletter at the same time? Yes. Select the newsletter in the post's distribution, and publishing emails it to subscribers who have given consent. The blog needs a sending domain, a From: address and a public address first. The email has the subject, the cover image when one is set, a summary and a link to the post, not the full body. See how publishing from Claude and ChatGPT works.

How do I send email from Claude or Claude Code? Connect the server as in Quick start, then ask for the email in plain words, for example "Email the March update to the beta-users group." Recipients who already consented get it right away. Anyone else gets a consent request, and the email goes out after they consent, when you send pending emails.

Which emails skip consent (transactional/OTP)? Only the built-in transactional templates: OTP code, MFA enrollment, new device login, password changed, email changed, order receipt and order completed. send_consentless_email sends them right away. Custom emails and custom templates always wait for consent.

How it compares

For side-by-side comparisons with other blog and newsletter platforms, see GoodSender vs WordPress, Ghost, beehiiv and Hashnode.

Telemetry & privacy

Telemetry is enabled by default, on the hosted server and on a server you run yourself. The MCP server sends usage and reliability metrics to GoodSender's own metrics and tracing systems (no third-party analytics vendor) to help improve the product.

Typical signals include:

  • The workspace identifier, MCP tool names, call counts, and latency.
  • Success and error rates.
  • On failures, the error message truncated to 512 characters.
  • Background job error codes and frequency.

Tool inputs and results (email bodies, recipient lists, template contents) are not recorded. An error message can still contain a fragment of what was passed to the tool, for example an email address that failed validation.

On a server you run yourself (MCP bundle, Docker, binaries or CLI), you can opt out of telemetry by setting GOODSENDER_TELEMETRY=false in the MCP server environment.

See the GoodSender Privacy Policy for how personal data is handled by the service, and the GoodSender Terms of Service for the terms of use.

OpenAI Plugin Directory package

The ZIP uploaded at platform.openai.com/plugins is generated in GitHub Actions, never by hand. Its sources live in openai-plugin/: the manifest template (plugin.template.json, version stamped per release), mcp.json (the hosted server https://mcp.goodsender.com/, OAuth with dynamic client registration), the icons, a get-started skill, the review test cases (test-cases.json, exactly 5 positive and 3 negative), the release notes and optional wording for annotation justifications.

scripts/openai-plugin/build.py validates every submission limit (text lengths, HTTPS URLs, square icons of 48–4096 px and at most 5 MiB, starter prompts, test-case counts) and builds the ZIP. The per-tool annotation justifications (ANNOTATIONS.md) are generated from the tools/list of the released server binary, which list_tools.py runs against a local mock of its startup session check, so the justifications always match the real hints.

  • Download: every published release carries goodsender-openai-plugin-<version>.zip, plus -ANNOTATIONS.md and -TEST_CASES.md, as release assets. To build one without a release, run the OpenAI plugin package workflow (Actions → Run workflow, optionally with a release tag) and download its artifact. Pull requests build it against the latest release.
  • Demo video: set the repository variable OPENAI_PLUGIN_DEMO_URL to stamp the reviewer demo URL into the package. Reviewer credentials are never in the package; enter them in the portal.
  • Domain verification: the portal shows a token for https://mcp.goodsender.com/.well-known/openai-apps-challenge. Put it in GOODSENDER_OPENAI_APPS_CHALLENGE in good-sender/hosted-mcp-deployment ansible/envs/prod.yml, deploy, then press Verify domain. The hosted server serves it as plain text. If the portal names the parent origin https://goodsender.com instead, the token must be served as a static plain-text file at /.well-known/openai-apps-challenge by goodsender-web.
  • Restricted data (reviewer note): OpenAI plugins must not handle one-time codes, passwords or other credentials. The ChatGPT listing, test cases and skill therefore describe only account notices and receipts. If a reviewer asks about the otp_code and mfa_enrollment templates of send_consentless_email, paste this into the portal's notes: "GoodSender's transactional templates deliver messages generated by the user's own application. One-time codes passed to otp_code / mfa_enrollment are created and verified by that application; GoodSender only renders and delivers the email. It does not store or check codes, and it never asks for or receives the user's own passwords, API keys or verification codes. These templates are not part of the ChatGPT listing or its test cases."

Links

Source: README.md at commit 22f065a

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

11
  1. v0.9.1LatestNov 3, 2026
  2. v0.9.0Oct 29, 2026
  3. v0.8.2Oct 24, 2026
  4. v0.8.1Oct 23, 2026
  5. v0.7.1Oct 20, 2026
  6. v0.7.0Oct 20, 2026
  7. v0.6.0-rc1Oct 8, 2026
  8. v0.5.2Oct 1, 2026
  9. v0.5.1Oct 1, 2026
  10. v0.5.0Sep 23, 2026
  11. v0.4.1-rc3Sep 16, 2026

Score

85% 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
  • License10 pts