CLI tool and MCP server to interact with Mailinator disposable email service
CLI tool and MCP server to interact with Mailinator disposable email service. Exposed over MCP by the mailinator cli mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A Node.js CLI tool and MCP (Model Context Protocol) server to interact with the Mailinator disposable email service. List emails in any inbox and retrieve individual messages in various formats, either from the command line or through AI assistants like Claude Desktop.
Everything the assistant can do here goes through one of these:
Inbox — GET https://api.mailinator.com/cli/v3/domains/{domain}/inboxes/{inbox_name}Email — GET https://api.mailinator.com/cli/v3/domains/{domain}/messages/{message_id}?format={format}list_inbox — The list_inbox tool exposed by this serverget_email — The get_email tool exposed by this serverWildcards — The Wildcards tool exposed by this serverDomains — The Domains tool exposed by this servermailinator-cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: MAILINATOR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mailinator Cli's toolset — Inbox, Email, list_inbox and 3 more — is a fair guide to whether it matches your workflow. It is maintained by manybrain; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Inbox | GET https://api.mailinator.com/cli/v3/domains/{domain}/inboxes/{inbox_name} |
| GET https://api.mailinator.com/cli/v3/domains/{domain}/messages/{message_id}?format={format} | |
| list_inbox | The list_inbox tool exposed by this server. |
| get_email | The get_email tool exposed by this server. |
| Wildcards | The Wildcards tool exposed by this server. |
| Domains | The Domains tool exposed by this server. |
{
"mcpServers": {
"mailinator-cli": {
"command": "npx",
"args": ["-y", "mailinator-cli"],
"env": {
"MAILINATOR_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MAILINATOR_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.