Log inSubmit server
Shipmail MCP logo

Shipmail MCP

Connects MCP-compatible agents to Shipmail custom-domain mailboxes, messages, calendars, webhooks, and related business email features.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Shipmail MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "shipmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "shipmail-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y shipmail-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

shipmail-mcp connects MCP-compatible agents to Shipmail, a business email platform for custom-domain inboxes and related workflows. It exposes Shipmail API capabilities over a hosted Streamable HTTP endpoint or a local stdio process, using a Shipmail API key for access. Agents can work with domains, mailboxes, messages, threads, webhooks, calendars, bookings, newsletters, and other account features. Reach for it when an agent needs its own business mailbox that can be shared with REST clients, webhooks, IMAP/SMTP clients, or human users.

Use cases

  • Create a dedicated custom-domain mailbox for an AI agent
  • Read and reply to business email through MCP
  • Trigger workflows from Shipmail webhooks
  • Manage newsletters, templates, and audiences
  • Coordinate calendars and booking pages from an agent

Key features

  • Hosted Streamable HTTP transport
  • Local stdio transport
  • Custom-domain mailbox access
  • Email messages and thread operations
  • Webhook and automation support
  • Calendar and booking management

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 17d ago via OSV.dev · shipmail-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.9kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.

How Shipmail MCP works

What shipmail-mcp does

shipmail-mcp exposes Shipmail’s business email API through the Model Context Protocol. It is intended for agents that need to operate custom-domain mailboxes rather than only send transactional messages or connect to an existing Gmail or Microsoft account.

The available Shipmail surface includes domains, mailboxes, messages, threads, webhooks, suppressions, email templates, audiences, newsletters, calendars, booking pages, automations, and organization members. A mailbox can also be used through Shipmail’s REST API, inbound webhooks, dashboard, IMAP, or SMTP, allowing agent activity to coexist with application code and human workflows.

How it works

The server supports two transports:

  • A hosted Streamable HTTP endpoint at https://shipmail.to/api/mcp.
  • A local stdio process for MCP hosts that launch the server themselves.

Both transports use Shipmail’s stateless MCP protocol dated 2026-07-28. The connecting MCP client must support that protocol. Clients using the older 2025 initialize handshake are rejected, so the MCP host may need an update before connecting.

Authentication uses a Shipmail API key. The key gives the agent access to the Shipmail account and resources permitted by that key. Shipmail’s API documentation covers creating and using API keys.

Setup and configuration

For a hosted connection, configure the MCP client to use the Shipmail Streamable HTTP endpoint and provide a Shipmail API key according to the client’s MCP configuration format.

For local stdio use, run the published package with Node.js 20 or newer:

Terminal
npx -y shipmail-mcp

The local process also requires a Shipmail API key. Client configuration details vary between MCP hosts, but the server can be used with Claude Desktop, Cursor, VS Code, Windsurf, and other MCP-compatible clients.

Tools and capabilities

The Shipmail API surface exposed to agents covers:

  • Custom domains and mailboxes
  • Email messages and conversation threads
  • Webhooks and suppression records
  • Reusable email templates
  • Audiences and newsletters
  • Calendars and booking pages
  • Automations
  • Organization members

These capabilities support agent-owned or dedicated business inboxes that can send, receive, read, and reply to email while remaining accessible through other Shipmail interfaces.

Limitations and notes

Protocol compatibility is a hard requirement: clients that use the legacy 2025 initialization handshake cannot connect. The local transport requires Node.js 20 or later, while the hosted transport avoids that local runtime requirement. Access depends on a valid Shipmail API key and the permissions associated with it.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Shipmail MCP

shipmail-mcp is an MCP server that connects AI agents to Shipmail custom-domain business email. Its tools cover domains, mailboxes, messages, threads, webhooks, templates, audiences, newsletters, calendars, booking pages, automations, suppressions, and organization members through hosted HTTP or local stdio.

Install it for local stdio use by running `npx -y shipmail-mcp` with Node.js 20 or newer. Configure your MCP client to launch that process and provide a Shipmail API key. Hosted use connects to `https://shipmail.to/api/mcp` instead.

Yes, shipmail-mcp works with Cursor. Configure Cursor to use either the hosted Streamable HTTP endpoint or the local stdio process, then authenticate with a Shipmail API key. Cursor must support the stateless MCP `2026-07-28` protocol.

shipmail-mcp supports Streamable HTTP and stdio. The hosted Streamable HTTP endpoint is `https://shipmail.to/api/mcp`; local deployments run the npm package as a stdio process. Both transports use Shipmail’s stateless MCP `2026-07-28` protocol.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewShipmail MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/shipmail-mcp?style=directory)](https://allmcps.com/mcp/shipmail-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/shipmail-mcp"><img src="https://allmcps.com/api/badge/shipmail-mcp?style=directory" alt="Shipmail MCP on AllMCPs" /></a>