--- title: "Freshly Minted: what's new in September" description: "Our September roundup with an MCP server for your AI assistant, scheduled emails, the Lettermint CLI, new SDKs and a batch of smaller improvements." url: "https://lettermint.co/blog/freshly-minted-whats-new-in-september" published: "2026-10-01" last_updated: "2026-10-01" --- # Freshly Minted: what's new in September > Our September roundup with an MCP server for your AI assistant, scheduled emails, the Lettermint CLI, new SDKs and a batch of smaller improvements. Welcome to the fourth edition of *Freshly Minted*, our monthly round-up of everything we've built at Lettermint, including the smaller improvements that never quite make it to the changelog. September closes out Q3, so we used it to finish what we started this summer. ![Lettermint MCP](https://lettermint.co/content/changelog/lettermint-email-mcp.gif) ## Your AI assistant now speaks Lettermint Lettermint has its own [MCP server](https://lettermint.co/docs/mcp). Connect Mistral, Claude, ChatGPT or any other AI tool that supports MCP, sign in with your Lettermint account, and ask your assistant about your sending. A few things you can ask: - *A customer says they never got their confirmation. Can you check?* - *How did last week's newsletter do?* - *Compare my sending figures for this month with last month.* [Transactional email](https://lettermint.co/features/transactional-emails) often carries sensitive content, so your assistant gets as little as possible. Personal data is hidden by default. It sees that an email went out and how it went, not what was in it or who received it. Only send newsletters without personal data? Switch on content access in your team settings. Your assistant only reaches the [projects you have access to](https://lettermint.co/changelog/give-team-members-and-clients-the-right-access-rbac), and it can't touch your tokens, team members or billing. [Read the changelog](https://lettermint.co/changelog/transactional-email-mcp-server). ![Lettermint scheduled emails](https://lettermint.co/content/changelog/lettermint-scheduled-emails.webp) ## Schedule emails up to 30 days ahead Until now, we sent every email the moment it came in. Anything meant for later needed a cron job or a delayed queue on your side. Now you send the email with a send time, and we hold it until then. Your [Black Friday campaign](https://lettermint.co/knowledge-base/deliverability/prevent-emails-spam-holidays-gmail-outlook) in November can go out at midnight without you sitting at your laptop. When someone books an appointment, you schedule the reminder for the day before right away. If they cancel, you pull the reminder. The send time can be a timestamp or [plain English](https://lettermint.co/docs/platform/emails/scheduling) like `tomorrow at 9am`. Scheduling works through the API, SMTP and our SDKs, and you can reschedule or cancel until the email goes out. Available on [Growth and Pro](https://lettermint.co/pricing). [Read the changelog](https://lettermint.co/changelog/schedule-your-emails-with-scheduled-emails). ![Lettermint CLI](https://lettermint.co/content/changelog/lettermint-cli-send.gif) ## Your email, from the terminal The [Lettermint CLI](https://lettermint.co/docs/cli) is here, for macOS, Linux and Windows. You sign in once through your browser, and the CLI keeps your login in your operating system's credential store instead of a config file. Send an email, check what happened to a message, or add and verify a domain without opening the dashboard. Testing webhooks gets easier too. Point the CLI at the app on your laptop and events arrive there directly, without a public tunnel or a temporary webhook. Each delivery shows up in your terminal with the status code your app returned. The CLI also includes a skill for AI coding agents, so they can send and inspect email without guessing. [Read the changelog](https://lettermint.co/changelog/transactional-email-cli). ## New SDKs, and a Terraform provider Community packages for .NET, Elixir and Symfony already existed, and they still work. We maintain the official ones ourselves, so every new Lettermint feature, like scheduled emails, lands in them too. - [.NET](https://lettermint.co/docs/guides/send-email-with-dotnet) - [Rust](https://lettermint.co/docs/guides/send-email-with-rust) - [Elixir](https://lettermint.co/docs/guides/send-email-with-elixir) - [Symfony Mailer](https://lettermint.co/docs/guides/send-email-with-symfony) - Terraform The .NET, Rust and Elixir SDKs also handle the Team API and webhook signature verification. You'll find all our SDKs on the [integrations page](https://lettermint.co/integrations). [Read the changelog](https://lettermint.co/changelog/new-sdks-for-dotnet-rust-elixir-and-symfony). ## Improvements & fixes Beyond the headliners, we polished a lot of smaller things too: - **Bounce and complaint forwarding**: have bounces and spam complaints forwarded to an email address per project, in standard formats. Handy for ticketing tools and systems that can't receive webhooks. - **Inbound quarantine**: [inbound email](https://lettermint.co/features/inbound-emails) our spam filter blocks now goes to quarantine instead of disappearing, so you can process anything that was flagged by mistake. - **Smarter suppressions**: an address that doesn't exist is now blocked across your whole team. A spam complaint blocks your broadcast routes, but not your [transactional email](https://lettermint.co/knowledge-base/product/difference-transactional-broadcast-emails). [See how it works](https://lettermint.co/docs/platform/emails/suppressions). - **DMARC for subdomains**: we now read the `sp=` tag and inherited [DMARC](https://lettermint.co/knowledge-base/definitions/what-is-dmarc) policies, so each [subdomain](https://lettermint.co/knowledge-base/deliverability/what-is-an-email-subdomain-and-when-should-you-use-one) gets the right policy. - **Share DNS instructions**: now also for tracking and inbound domains. - **Dashboard details**: clearer tooltips, a better preview of the message behind a suppression, and DNS instructions that show exactly which part of a record to update. Several of these started as a message from someone using Lettermint, the Terraform provider and shareable DNS instructions among them. So keep them coming, through the dashboard or [Discord](https://lettermint.co/r/discord). We read every message. *See you in October, when the clocks go back and your cron jobs get confused.*