
Mailsink
io.github.heocoiPublished by GitHub account heocoiv0.1.5Updated Oct 24, 2026
Disposable inboxes for AI agents and CI: catch the verification email, read the OTP or link.
Overview
MailSink MCP gives an assistant disposable email inboxes so it can receive signup emails, read OTP codes and magic links, and clean up afterwards.
- What you can do
- Create and list temporary inboxes, each returning an address, ID and expiry time, and delete an inbox when done with it. Wait for an incoming email, with a timeout of up to 120 seconds. Extract the most recent one-time verification code or magic link from an inbox. List message summaries in an inbox and read the full content of a specific message by ID.
- When to use it
- Useful when an assistant or test automation needs to complete a signup or login flow that requires email verification, such as capturing an OTP or confirmation link, without setting up webhooks, IMAP credentials or MIME parsing.
- Requirements
- Runs locally as an npm package (Node.js), installed globally or via npx, and configured in an MCP client such as Claude Code, Claude Desktop, Cursor or Windsurf. Requires a MailSink account and an API key supplied in the MAILSINK_API_KEY environment variable; MAILSINK_API_URL optionally overrides the API base URL. Network access to the MailSink API is needed.
Installation
In SourceWeft
- Open Mailsink in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@mailsink/mcp
Model Context Protocol server for MailSink — programmatic temporary email inboxes for AI agents and test automation.
Gives your agent eight typed tools for provisioning disposable addresses, waiting on signup emails, extracting OTP codes and magic links, and cleaning up after itself. Works in Claude Code, Claude Desktop, Cursor, Windsurf, and any other MCP-aware client.
Install
Or run via npx without installing:
Get an API key
-
Sign in at https://mailsink.dev/app with GitHub.
-
Copy the key from the one-time reveal. Store it in your password manager or
.env. -
Export it so the MCP server can read it:
Free tier is 50 inboxes/month and includes MCP. Pro ($15/mo) and Team ($49/mo) lift the inbox cap, raise email size limits, extend TTL, and bump request rates. See pricing.
Configure your client
Claude Code
Claude Desktop / Cursor / Windsurf
Add to the mcpServers section of the client's config file:
Restart the client. You should see the mailsink server listed with its
eight tools.
Tools
Example agent flow
No webhook plumbing. No IMAP credentials. No parsing MIME.
Environment variables
MAILSINK_API_KEY(required) — your account's API key.MAILSINK_API_URL(optional, defaulthttps://api.mailsink.dev) — override for self-hosted or dev API.
Source
https://github.com/heocoi/mailsink/tree/main/mcp
License
MIT — see LICENSE.
Source: README.md at commit 1df0da2
Tools
0Version history
1- v0.1.5LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts