SMTP2GO pricing: free for 1,000 emails, $10 a month for 10,000 and $75 for 100,000

Three volumes: 1,000, 10,000 and 100,000 emails

• 1,000 emails a month: free. Enough for an app that sends a few messages a day, with the daily cap described below.
• 10,000 emails a month: $10. That is $1.00 per thousand, and the same $1 per thousand is what Starter charges for every extra thousand, so going past the allowance costs as much as the plan did per email.
• 100,000 emails a month: $75. That averages $0.75 per thousand and is the first plan with a dedicated IP address. The page's slider also has stops at 40K, 250K, 500K and 1M emails whose prices were not read for this guide, so take those off the slider rather than from a formula.

Because Starter's overage ($1 per thousand) is more than Professional's average, anyone who regularly goes well past 10,000 emails should price Professional before paying overage month after month. Yearly billing is ten months for twelve on both plans ($100 against $120, and $750 against $900), which suits steady senders more than seasonal ones.

What the free plan really allows

The pricing page says 1,000 emails a month with no card. The API rate-limiting page adds the constraint that decides whether it works: a limit of 200 emails a day, with a further 25 per hour until a sender domain is verified. It also gives free accounts five days of reporting against 30 on paid plans, limits support to tickets after the first 14 days, and lists email overage, subaccounts and dedicated IPs among the things you gain by upgrading.

Paid accounts start under review. The same page says new paid accounts get a temporary quota of 1,000 emails a day, and anything sent beyond it during the one-time review is held in the queue and released once the account is activated. Plan a first big send around that, not around the 10,000 or 100,000 on the price card.

SMTP relay limits that shape the plan choice

SMTP2GO is a relay first. The relay documentation gives the server as mail.smtp2go.com, with TLS on ports 25, 2525, 8025, 587 and 80, and SSL on 465, 8465 and 443. You need a verified sender and an SMTP user whose username and password you create in the app, or you can use IP or address authentication on paid plans. The listed limits are a 50 MB maximum message size including attachments, 400 recipients per email (the docs suggest staying under 50 to 100), a default sending speed of 200,000 emails an hour, 40 simultaneous connections and 5,000 emails per connection.

Two details matter for modern workflows. Email templates are only supported when sending through the API, not through SMTP relay, and SMTP2GO's templates guide says test emails sent from a template count against your email allowance. On a free plan capped at 200 a day, iterating on a template with ten test sends is not free.

Three ways AI-written copy reaches SMTP2GO

If you draft with Lavender, MailMaestro, Jasper, Copy.ai or a chatbot, SMTP2GO never sees the drafting. It receives a finished message, and its documentation describes three ways to hand one over.

The template route suits a chatbot draft best, because the HTML is stored once and the app supplies only the variables. The docs say variables go inside double braces, as {{ variable_name }}, and that HandleBarsJS is supported. A send that uses the documented example template looks like this.

POST https://api.smtp2go.com/v3/email/send
{
  "sender": "hello@yourdomain.com",
  "to": [ "jane@example.com" ],
  "version": 1,
  "template_id": "userwelcome",
  "template_data": {
    "username": "jane",
    "plan": "deluxe"
  }
}

AI tooling SMTP2GO documents: an MCP server and an agent skill

SMTP2GO's pricing page does not describe a writing assistant, and it lists no campaign editor or journey builder, only SMS messaging, subaccounts, scheduled reporting, a dedicated IP and email testing tools. Its AI material sits in the developer docs. The MCP page describes a remote server at developers.smtp2go.com/mcp with five tools: list-endpoints, get-endpoint, search-endpoints, execute-request and get-server-variables. Only execute-request is a write tool, and the docs warn that it can perform real actions, including sending email if the key allows it. They recommend a dedicated, narrowly scoped API key with the permissions /email/send, /allowed_senders/view and /domain/view, passed in an X-Smtp2go-Api-Key header, with a bearer-token alternative added so Claude Desktop connectors can authenticate.

The Skills page describes the other option: an agent skill called smtp2go-send-email, installed from the smtp2go-oss/skills repository on GitHub, that sends transactional, test, scheduled, template, HTML or plain-text email through the API. The page calls the catalog new and not yet published to a skill registry. Choose MCP when you want an agent to explore the whole API, and a skill when you want one focused action such as sending. Neither feature is tied to a price tier on the pricing page, and the free plan's 200-a-day cap applies to whatever an agent sends.

Who SMTP2GO suits, and who should look elsewhere

Pick it if you already have an application, a WordPress site or a mail client that speaks SMTP and you want delivery handled with phone and chat support on paid plans. The docs menu also lists a WordPress plugin and a cPanel/WHM plugin. Starter at $10 is cheap insurance for a small product, and the 30-day refund promise lowers the risk of trying it.

Look elsewhere if the people editing emails are not developers. MailerSend has drag-and-drop and HTML builders with an MCP server that can create templates, and Postmark and Mailgun are the other developer-first senders in this index. If you need journeys, segments or product-event triggers, none of the relay-style tools covers that, and the pricing index points to platforms that do. The method page explains how these figures are read and dated, and the writing-assistant comparison covers the tools that write the copy.

FAQ