Integration
Sim.ai Email Integration
Attach Dead Simple Email's MCP server to Sim.ai Agent blocks with zero code. Your canvas agents get 14 email tools — inboxes, sending, reading, replies, and OTP extraction.
How It Works
Sim.ai is an open-source canvas for building agent workflows visually, and MCP servers are its plug-in mechanism for external tools: configure a server once in workspace settings, and its tools become available to every Agent block. Dead Simple Email runs a hosted MCP server, so the whole integration is a form, not a codebase.
Honest framing: there is no dedicated Dead Simple Email block in Sim's toolbar as of August 2026. You don't need one — the MCP route below gives Agent blocks the full toolset, and a Function block can hit the REST API directly for fixed steps.
Connect the MCP Server (No Code)
- Store your API key. In Sim, add an environment variable named
DSE_API_KEYwith yourdse_...key so it never sits in plain text in the server config. - Add the server. Open your workspace settings, go to MCP Servers, and click Add Server (you need Write permission).
- Fill in the connection:
# Sim workspace settings → MCP Servers → Add Server Name: deadsimple-email Transport: Streamable HTTP URL: https://api.deadsimple.email/mcp # Headers Authorization: Bearer {{DSE_API_KEY}}
- Test the connection. Click Test Connection before saving — Sim should report the server is reachable and discover 14 tools.
- Attach tools to an Agent block. On your canvas, open an Agent block's tool picker and select the Dead Simple Email tools you want the agent to use. The agent then decides when to call them from conversation context.
Sim resolves {{DSE_API_KEY}} from your environment variables at request time, and each server card lists its tools with parameter names and types. If we add tools later, click Refresh on the server card to pull the latest schemas.
The 14 Tools Your Agent Blocks Get
| Tool | Description |
|---|---|
create_inbox | Create a new inbox with its own email address |
list_inboxes | List all inboxes on the account |
delete_inbox | Delete an inbox and its messages |
send_email | Send an email from an inbox |
read_messages | List recent messages in an inbox |
read_message | Read a single message with full body |
reply_to_message | Reply in-thread (threading handled automatically) |
forward_message | Forward a message to another address |
wait_for_email | Block until a matching email arrives |
get_verification_code | Wait for and extract an OTP / verification code |
get_verification_link | Wait for and extract a verification / magic link |
list_threads | List conversation threads |
read_thread | Read a full conversation thread |
get_usage | Check plan usage and limits |
A typical canvas: a trigger starts the workflow, an Agent block drafts and sends outreach with send_email, and a later Agent block checks the thread with read_thread and drafts the reply. Selecting only the tools each block needs keeps the agent's choices predictable.
Alternative: REST from a Function Block
For deterministic steps where you don't want an LLM choosing tools — "always send exactly this email" — call the REST API from a Function block instead:
// Sim resolves {{DSE_API_KEY}} from environment variables const res = await fetch( "https://api.deadsimple.email/v1/inboxes/inb_your_inbox/messages", { method: "POST", headers: { Authorization: "Bearer {{DSE_API_KEY}}", "Content-Type": "application/json", }, body: JSON.stringify({ to: ["user@example.com"], subject: "Your workflow finished", text_body: "All 3 steps completed successfully.", }), } ); return await res.json();
The full REST surface — inbox CRUD, threads, webhooks, domains — is documented in the API reference.
Frequently Asked Questions
Yes, through MCP. Sim lets you attach MCP servers to Agent blocks with no code. Add our hosted server in workspace settings and your agents can create inboxes, send and read email, reply in threads, and wait for verification codes — 14 tools in total.
No. The MCP connection is pure configuration: URL, transport, and an Authorization header. Sim discovers the tools automatically. Code only enters the picture if you prefer calling the REST API from a Function block for deterministic steps.
No — as of August 2026 there is no dedicated block. The MCP server route provides the same capability without one, which is exactly what Sim's MCP support is designed for.
Yes. Sim is open source, and its MCP support works the same self-hosted: your instance connects out to https://api.deadsimple.email/mcp over HTTPS, so it only needs outbound internet access.
Yes. The free tier includes 5 inboxes and 5,000 emails per month, requires no credit card, and does not expire.