Bring Disposable Email
to Claude Desktop
Learn how to connect Mailsac to Claude Desktop and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Mailsac MCP Server?
Connect your Mailsac account to any AI agent to automate your email testing and inbox management. This MCP server enables your agent to reserve private email addresses, retrieve and search for messages, and inspect HTML or plain text bodies directly from natural language interfaces.
What you can do
- Inbox Oversight — List and manage your reserved (enhanced) addresses and custom domains
- Instant Retrieval — Fetch a list of messages received by any address in your account instantly
- Content Extraction — Retrieve sanitized HTML or raw plain text bodies to extract verification codes or links
- Inbox Maintenance — Permanently delete individual messages or clear entire inboxes via simple commands
- Infrastructure Management — Reserve new private addresses programmatically for isolated testing flows
- Global Search — Query messages across all your addresses using advanced search parameters (requires paid tier)
How it works
1. Subscribe to this server
2. Enter your Mailsac API Key
3. Start managing your disposable inboxes from Claude, Cursor, or any MCP-compatible client
Who is this for?
- QA Engineers — Automate the extraction of email-based verification codes for testing suites
- Developers — Quickly inspect incoming test emails and manage temporary addresses directly from your IDE
- Privacy-Conscious Users — Manage temporary communication channels via simple natural language commands
Built-in capabilities (9)
Permanently remove a message from an inbox
Get the sanitized HTML body of a specific message
Get the plain text body of a specific message
List custom domains linked to the account
List messages in a specific inbox
List all reserved (enhanced) email addresses
Delete/Release a reserved email address
Reserve a specific email address
Requires a paid Mailsac tier. Use query params like to, from, subject. Search for messages across all addresses
Why Claude Desktop?
Claude Desktop is the definitive way to connect Mailsac to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Mailsac in Claude Desktop
Mailsac and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mailsac to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Mailsac in Claude Desktop
The Mailsac MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Mailsac for Claude Desktop
Every tool call from Claude Desktop to the Mailsac MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is an 'Enhanced' address in Mailsac?
An enhanced address is a private inbox that only you can access. Use the reserve_new_address tool to make an address private/enhanced.
Can I read the raw SMTP source of an email?
While this server provides tools for HTML and Plain Text bodies, the Mailsac API supports raw data retrieval. You can use the text body tool to extract key technical metadata.
Is an API Key required for all addresses?
Yes, this MCP server requires an API Key to interact with your account and access your reserved resources and private messages.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.