Server data from the Official MCP Registry
Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks.
Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks.
Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
3 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: SHIPMAIL_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-jcoulaud-shipmail-mcp": {
"env": {
"SHIPMAIL_API_KEY": "your-shipmail-api-key-here"
},
"args": [
"-y",
"shipmail-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Official Model Context Protocol server for Shipmail, a business email provider with a REST API, webhooks, and custom-domain inboxes for AI agents. Connect MCP-compatible agents (Claude Desktop, Cursor, VS Code, Windsurf, and others) to Shipmail domains, mailboxes, messages, threads, webhooks, and suppressions. The public source repository is jcoulaud/shipmail-mcp, which is also the npm package metadata target.
Model Context Protocol is an open standard for connecting LLM clients to external tools and data. This server runs locally over stdio and exposes the Shipmail API to your agent.
Transport: stdio (local). Requirements: Node.js 20+ and a Shipmail API key.
shipmail-mcp when an AI agent needs its own custom-domain email inbox that it can send from, read, and reply from.shipmail-mcp on npm.Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"shipmail": {
"command": "npx",
"args": ["-y", "shipmail-mcp"],
"env": {
"SHIPMAIL_API_KEY": "sm_live_..."
}
}
}
}
Restart Claude Desktop. The Shipmail tools appear under the tools menu.
Add to .cursor/mcp.json in the project root, or ~/.cursor/mcp.json for global use:
{
"mcpServers": {
"shipmail": {
"command": "npx",
"args": ["-y", "shipmail-mcp"],
"env": {
"SHIPMAIL_API_KEY": "sm_live_..."
}
}
}
}
Add to .vscode/mcp.json. The inputs block prompts for the key on first use instead of storing it in the file:
{
"inputs": [
{
"type": "promptString",
"id": "shipmail-api-key",
"description": "Shipmail API key",
"password": true
}
],
"servers": {
"shipmail": {
"type": "stdio",
"command": "npx",
"args": ["-y", "shipmail-mcp"],
"env": {
"SHIPMAIL_API_KEY": "${input:shipmail-api-key}"
}
}
}
}
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"shipmail": {
"command": "npx",
"args": ["-y", "shipmail-mcp"],
"env": {
"SHIPMAIL_API_KEY": "sm_live_..."
}
}
}
}
Once connected, ask your agent:
support@acme.com and turn on auto-reply with this text..."support@acme.com from this week and summarize what needs attention."thread_abc123 confirming we ship Friday."https://example.com/hooks/shipmail, then send a test event."whk_xyz and flag any that failed."All tools are namespaced with shipmail_ to avoid collisions with peer MCP servers.
| Group | Tools |
|---|---|
| Status | shipmail_status |
| Domains | shipmail_list_domains, shipmail_get_domain, shipmail_create_domain, shipmail_update_domain, shipmail_delete_domain, shipmail_verify_domain, shipmail_search_domains |
| Mailboxes | shipmail_list_mailboxes, shipmail_get_mailbox, shipmail_create_mailbox, shipmail_update_mailbox, shipmail_delete_mailbox, shipmail_list_mailbox_folders, shipmail_create_mailbox_folder, shipmail_update_mailbox_folder, shipmail_delete_mailbox_folder, shipmail_list_mailbox_identities, shipmail_get_mailbox_rules, shipmail_set_mailbox_rules, shipmail_reset_mailbox_password, shipmail_set_auto_reply, shipmail_set_spam_filter |
| Mailbox inbox | shipmail_list_mailbox_inbox_messages, shipmail_get_mailbox_inbox_thread, shipmail_update_inbox_message, shipmail_move_inbox_message, shipmail_delete_inbox_message |
| Messages and threads | shipmail_list_messages, shipmail_get_message, shipmail_send_message, shipmail_reply_to_message, shipmail_list_threads, shipmail_get_thread, shipmail_reply_to_thread |
| Webhooks | shipmail_list_webhooks, shipmail_get_webhook, shipmail_create_webhook, shipmail_update_webhook, shipmail_delete_webhook, shipmail_rotate_webhook_secret, shipmail_test_webhook, shipmail_list_webhook_deliveries |
| Suppressions | shipmail_list_suppressions, shipmail_remove_suppression |
To restrict the surface, pass --tools (overrides SHIPMAIL_MCP_TOOLS):
{
"args": [
"-y",
"shipmail-mcp",
"--tools",
"shipmail_list_mailboxes,shipmail_get_thread,shipmail_reply_to_thread"
]
}
Read-only resources for inspection without tool calls:
shipmail://account/statusshipmail://domainsshipmail://domains/{id}shipmail://mailboxesshipmail://mailboxes/{id}shipmail://mailboxes/{id}/foldersshipmail://mailboxes/{id}/identitiesshipmail://mailboxes/{id}/rulesshipmail://mailboxes/{id}/inbox/messagesshipmail://mailboxes/{id}/inbox/threads/{thread_id}shipmail://messages/{id}shipmail://threads/{id}Pre-built prompts the agent can use as guided workflows:
setup_domain: connect a new domain and walk through DNS setup.triage_mailbox: read recent threads in a mailbox and summarize what needs attention.draft_email_reply: draft a reply for a given thread, ready for user review.configure_webhook: set up and test a webhook for incoming events.| Variable | Required | Description |
|---|---|---|
SHIPMAIL_API_KEY | Yes (or SHIPMAIL_API_KEY_FILE) | Shipmail API key (sm_live_...). |
SHIPMAIL_API_KEY_FILE | No | Path to a file containing the API key. Takes precedence over SHIPMAIL_API_KEY. Reduces env-trace leak surface (Docker secrets, systemd LoadCredential). |
SHIPMAIL_BASE_URL | No | Override the API base URL. Must be https on a shipmail.to host. Defaults to https://shipmail.to/api/v1. |
SHIPMAIL_MCP_TOOLS | No | Comma-separated tool allowlist. The --tools flag overrides this. |
SHIPMAIL_ALLOW_INSECURE_BASE_URL | No | Set to 1 to permit a non-https or non-shipmail.to base URL. Local development only. |
SHIPMAIL_MCP_DEBUG | No | Set to 1 to include request_id and status in stderr tool-call logs. |
shipmail_ to avoid collisions with peer MCP servers in the same host.structuredContent.idempotency_key. When omitted, the server generates a fresh key per tool call. Supply your own key if a specific request must stay idempotent across MCP retries.request_id is preserved for support. Generic Error thrown values (network errors, deserialization) are redacted to "Internal MCP error" before reaching the LLM. Detail lands on stderr.0.0.0.0, decimal-int IPs, .local, and .internal hosts are rejected at input time.destructiveHint. Hosts that gate on this annotation will prompt the user. Annotated tools include shipmail_update_domain, shipmail_update_webhook, shipmail_rotate_webhook_secret, shipmail_delete_mailbox_folder, shipmail_set_mailbox_rules, shipmail_reset_mailbox_password, and shipmail_set_auto_reply in addition to obvious deletes.Domain purchase is intentionally excluded.
destructiveHint:true tools.SHIPMAIL_API_KEY and held in memory by this process. If the host is compromised, the key is gone regardless. Rotate keys you suspect have been exposed.shipmail_create_webhook and shipmail_rotate_webhook_secret return the secret in structuredContent. Many MCP clients persist tool output in conversation history. Treat the session log as sensitive after these calls.This server forwards email subject lines, bodies, headers, attachment metadata, and recipient lists to whatever LLM you connect it to. The LLM provider may log that content. For privacy-sensitive workflows, restrict the tool surface with --tools so the LLM only sees what it needs.
SHIPMAIL_API_KEY is not set.
Confirm the host config includes the key in the env block, then restart the host.
Base URL must be https on a shipmail.to host.
You set SHIPMAIL_BASE_URL to something else. For local development, also set SHIPMAIL_ALLOW_INSECURE_BASE_URL=1.
Tools do not show up in the host.
Confirm the package launched. Most hosts surface a server log near the chat input or in a developer panel. Set SHIPMAIL_MCP_DEBUG=1 to add request_id and status to stderr.
Internal MCP error.
A non-API error (network, deserialization) was redacted before reaching the agent. Check the host's stderr panel for the underlying detail.
Rate limit hit mid-session. The per-session circuit breaker tripped. Restart the MCP server (in most hosts: toggle the server off and back on, or restart the host).
Webhook URL rejected.
URLs must be public https. Localhost, RFC1918, .local, and .internal are blocked at input time. Use a public tunnel (ngrok, cloudflared) for local testing.
For public source, tests, and issue tracking, use the standalone repository: github.com/jcoulaud/shipmail-mcp.
Install dependencies with Bun:
bun install
Run the server locally against the published Shipmail SDK:
SHIPMAIL_API_KEY=sm_live_... bun run dev
Run the standalone checks:
bun run typecheck
bun test
bun run build
The OpenAPI coverage test uses fixtures/openapi.json, copied from
https://shipmail.to/openapi.json when this public source repo is synced.
MIT.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.