LabscoMCP early access ↗
shipmail-toMCP SERVER · OFFICIAL PROJECT

Shipmail MCP

Give an agent a real mailbox on your own domain — send, read, reply, and hand the thread back to a human.

by shipmail-to ↗Email: Mailboxes & Delivery✓ Official

LABSCO SUMMARY

The draft-then-approve path is the one to build on.

An agent with unrestricted send is a liability; this server's answer is a reply draft that records the thread version it was written against and refuses to send if the conversation changed before you approved. Combined with scopes set outside the agent and a sandbox on test keys, that makes it practical to let something autonomous near a mailbox. Check your client's protocol version first — the strict 2026-07-28 requirement will reject an older host before you get to any of this.

What it is

The official MCP server for Shipmail, a business email host with a REST API, webhooks and custom-domain inboxes. Rather than bridging an existing Gmail or Outlook account, it hosts the mailbox itself, so the same inbox is reachable from agent tools, your application code, the dashboard and ordinary IMAP or SMTP clients.

What you get

  • Mailbox lifecycle under shipmail_ names — create, update, suspend and resume mailboxes, manage folders, identities, forwarding, app passwords, auto-reply and spam filtering
  • Domains end to end: shipmail_create_domain, shipmail_get_domain_dns_records for the records to add, then shipmail_verify_domain
  • Reading and replying — shipmail_list_mailbox_inbox_threads, shipmail_get_mailbox_inbox_thread, shipmail_create_inbox_reply_draft and shipmail_send_inbox_reply_draft, which rejects a stale draft if the conversation moved on before approval
  • Sending and scheduling — shipmail_send_message, plus list, inspect, replace and cancel on scheduled messages before dispatch starts
  • Attachments without base64 in the transcript: shipmail_prepare_staged_attachment_upload returns a five-minute, one-time upload URL that does not carry your credential
  • Webhooks as first-class tools — create, test, rotate the secret, list deliveries and replay one
  • Audiences and newsletters, including subscriber management, preflight checks and scheduling
  • Read-only resources such as shipmail://mailboxes and shipmail://domains, and four guided prompts: setup_domain, triage_mailbox, draft_email_reply and configure_webhook
  • A sandbox mode on test keys, where sends accept a sandbox_outcome and inbound mail can be faked without reaching a real recipient

Requirements

A Shipmail API key. The hosted server at https://shipmail.to/api/mcp needs nothing installed and supports OAuth as well as a bearer key; the local stdio route is the npm package shipmail-mcp, version 0.7.3, with SHIPMAIL_API_KEY set, and needs Node.js 20+. The client must speak the stateless MCP 2026-07-28 protocol — clients that still open with the 2025 handshake are rejected. What the agent may do is set by the key's scopes or the OAuth connection, and the server discovers that catalog before startup, failing closed if discovery fails.

Setup effort

One command plus a key — npx -y shipmail-mcp, then supply credentials