# shipmail-mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/shipmail-to/shipmail-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1854  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/shipmail-mcp

## Description
Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "shipmail-mcp": {
    "command": "npx",
    "args": ["-y","shipmail-mcp"]
  }
}
```

## Documentation

## 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:

```bash
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.

_Full upstream README: https://allmcps.com/mcp/shipmail-mcp/readme_