Add transactional email, form-to-email and inbound replies to a Repl over one clean REST API or the SDKs — and hand the Replit agent the full MCP tool surface. One key, kept in Secrets.
# Python, in a Repl — store DRIN_API_KEY in Secrets import os, requests requests.post( "https://api.drin.run/v1/emails", headers={"Authorization": f"Bearer {os.environ['DRIN_API_KEY']}"}, json={ "from": "hello@yourapp.com", "to": "user@acme.com", "subject": "Welcome", "text": "It works.", }, ) # → 202 Accepted { "id": "msg_8fK2q1", "status": "queued" }
Sign up free, add three DNS records, and your domain authenticates itself — so mail from the Repl reaches the inbox.
Put DRIN_API_KEY in the Repl's Secrets pane and read it from the environment — never commit it into the Repl's files.
Call the endpoint from your code, or point Replit Agent at the Drin MCP server to let it send and triage for you.
POST /v1/emailshttps://api.drin.run/v1One REST call or an SDK import sends transactional mail from a Python, Node or Bun Repl — keep the key in Secrets.
Wire a form in your Repl to one endpoint and submissions land in your inbox, with no separate backend to host.
Receive parsed inbound mail back into the Repl, routed by address — so a bot or app can read and reply.
Connect Replit's agent to the Drin MCP server and it gets the full 54-tool surface to send, triage and reply.
Grab a key, drop in one REST call, and your Repl sends real mail. Test in the sandbox; production starts at $3 a month.