list_inboxLABSCO SUMMARY
The unlock is `links`, not the mail reader.
An end-to-end signup test stalls at the point where a human has to open an email and click a link. Asking for a message in links format returns the URLs on their own, so the agent can carry on without anyone opening a mail client. Two limits worth knowing up front: wildcard inbox searches (test*) are private-domain only and need a token, and inbox names are capped at 50 characters of alphanumerics and dots.
What it is
A Mailinator client that runs either as a command-line tool or as an MCP server. It lists what has arrived in a disposable inbox and fetches individual messages in whichever shape you need — plain text, HTML, headers, the link list, or the SMTP delivery log.
What you get
list_inboxreturns the messages in an inbox, taking aninbox_nameand an optionaldomainget_emailfetches one message by ID, with aformatargument coveringsummary,text,textplain,texthtml,full,raw,headers,smtplog,linksandlinksfull- Read-only resources at
mailinator://inbox/{domain}/{inbox_name}andmailinator://email/{domain}/{message_id}for passive context linksreturns the URLs found in a message as a numbered list — the fast path to a verification link- An inbox cache at
~/.config/mailinator/inbox-cache.jsonlets you refer to messages by their listing number and auto-detects the domain - A health endpoint at
GET http://127.0.0.1:8080/healthwhen running in server mode
Requirements
Node.js >= 18.0.0 and an internet connection. Published on npm as mailinator-cli version 1.0.1, installed globally or run with npx mailinator-cli. The public domain needs no credentials at all; private domains, wildcard searches and SMTP logs need a Mailinator API token supplied as MAILINATOR_API_KEY or in ~/.config/mailinator/config.json. Server mode starts with --start-mcp-server and listens on 127.0.0.1 port 8080 by default, with --host and --port to change that; the MCP endpoint is POST http://127.0.0.1:8080/mcp.
Setup effort
One command — npm install -g mailinator-cli
USE CASES
Finishing a signup flow that ends in a confirmation email
List the test inbox, pull the newest message as a link list, and follow the verification URL.
Checking a password-reset mail actually went out
Read the inbox for the test account and look at the subject and sender without leaving the conversation.
Debugging why a message never arrived
Ask for the SMTP delivery log on a message to see what the sending side reported.
Inspecting the HTML a template actually produced
Fetch the same message as texthtml or headers to check rendering and routing separately.
2 tools
Listed in project docs. Your client may show a different list.
get_emailBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npm on PATH
- Node.js >= 18.0.0
INSTALLATION
Connect your client
Server setup
npm install -g mailinator-cliMCP Clients
Any MCP client
mailinator-cli --start-mcp-server{
"mcpServers": {
"mailinator": {
"url": "http://127.0.0.1:8080/mcp"
}
}
}