How to Send Email via Claude Desktop

#mcp #claudedesktop #permissionloop #emailapi

How to Send Email from Claude — Free, in Two Minutes

Two minutes from now, Claude Desktop will send a real email through your own account. This guide is for Claude Desktop users with a GoodSender account who want to wire up email via MCP. GoodSender is free for the first 100,000 emails per month, no credit card required.

Prerequisites

Claude Desktop installed.
A GoodSender account — sign up free, no credit card.

Step 1: Install the MCP Server

Download goodsender.mcpb from the latest GitHub release. Double-click it. Claude Desktop registers the server automatically.

Using a different AI client like Cursor? You'll need the Docker or manual binary path — see the MCP server docs.

Step 2: Add Your API Key

Grab your API key from the GoodSender dashboard. Paste it into the configuration prompt Claude Desktop shows after install.

Before sending, make sure you've also verified your sending domain in the GoodSender dashboard.

Flow 1: Compose and Send a Custom Template

In Claude Desktop, ask Claude to create a "weekly update" template using the MCP template composer:

Create a new email template called "Weekly Update" with a subject line "Your weekly update from Awesome App" with a futuristic design using GoodSender MCP

Claude opens the MCP template composer and builds the template with your variables. Once you're happy with it, ask Claude to send it:

Send the Weekly Update template to me at you@example.com.

A note on consent: Custom sends to recipients require the Permission Loop. GoodSender requests consent from the recipient first — outbound messages queue locally until consent is granted. Once a recipient approves, subsequent sends from your domain go through instantly. That earned permission is what keeps deliverability compounding rather than degrading over time.

Flow 2: Send a Transactional OTP Email

Transactional templates are the contrast case — no template setup, no consent step, and they fire instantly. In Claude Desktop, paste this prompt:

Send an OTP code to me at you@example.com.

Claude picks the GoodSender MCP, calls the transactional template endpoint, and the email lands in your inbox instantly. Transactional templates ship without a consent step, so there's no queue and no setup — the send goes through the moment Claude calls the tool.

Flow 3: Schedule a One-Time Send

Claude Desktop (in Cowork mode) has a built-in scheduler. You can use it to schedule a one-time send of the Weekly Update template for Monday at 10am — GoodSender's MCP handles the actual send when the scheduled time fires.

Schedule a one-time send of the Weekly Update template to you@example.com for Monday at 10am. Use headline "Monday briefing" and "Here's what's coming up this week."

What You Can Do Next

Now that you've got email working from Claude, the best thing to do is try it with your own use case. Send an OTP to a real user, schedule a weekly update, or write an email in Markdown and watch it render perfectly across 90+ inbox clients. The setup is already done — the rest is just asking Claude.

Why GoodSender for This

Free for 100,000 emails per month, no credit card. Consent and engagement are built into the API — the Permission Loop gates custom sends on explicit recipient consent, and the Engagement Check monitors recipient activity over time — so deliverability compounds rather than degrades. It runs on the same IP infrastructure Laneful uses for the world's largest senders.