I gave my AI agent the ability to send email

A developer connected Claude to email infrastructure using the Model Context Protocol (MCP), enabling the AI agent to check domain status, send emails, and read delivery events directly from chat. The setup uses SMTPfast's hosted MCP endpoint, requiring only a single command or config snippet. The developer warns that while agents excel at chaining tool calls, they lack restraint, and approval steps are critical for send-capable tools.

Last month I wired Claude up to my email infrastructure. Not "Claude writes an email draft and I paste it somewhere" but the agent checks my domain status, sends the email, and reads back the delivery events, all from the chat. The glue that makes this possible is MCP Model Context Protocol , and the whole setup takes about five minutes. Here is exactly how to do it, plus what surprised me once agents could actually touch production infrastructure. MCP is a small JSON-RPC protocol that lets an AI client Claude, Cursor, Windsurf, your own agent call tools exposed by a server. The server describes its tools with JSON schemas, the model picks a tool and fills in the arguments, and the client executes the call. The important design decision is where the server runs. A lot of MCP servers are local stdio processes you install per machine. For anything talking to a hosted API, a hosted MCP server is the better shape: nothing to install, your API key is the auth, and every client that speaks HTTP can use it. I use SMTPfast https://smtpfa.st for transactional email, which ships a hosted MCP endpoint at https://smtpfa.st/api/mcp . That is what I will use in the examples, but the pattern applies to any hosted MCP server. One command: claude mcp add --transport http smtpfast https://smtpfa.st/api/mcp \ --header "Authorization: Bearer sf your api key" For Cursor, it is a snippet in .cursor/mcp.json : { "mcpServers": { "smtpfast": { "url": "https://smtpfa.st/api/mcp", "headers": { "Authorization": "Bearer sf your api key" } } } } That is the entire installation. No npm package, no local process, no version drift between machines. MCP servers self-describe. You can poke one with curl to see the tool list: curl -sS https://smtpfa.st/api/mcp \ -H "Content-Type: application/json" \ -H "Authorization: Bearer sf your api key" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' The SMTPfast server exposes eight tools: send email , list emails , get email , list domains , verify domain , list suppressions , get analytics , and list contacts . The model reads those schemas and figures out the rest on its own. With the server connected, I can type things like this into Claude: "Check if my domain is verified, then send a test email from hello@mydomain.com to my personal address and tell me when it is delivered." Behind the scenes the agent calls list domains , sees the DKIM status, calls send email , waits, then calls get email to read the delivery events. I watch each tool call go by and approve it. No SDK, no glue code, no copy-pasting message IDs. The debugging workflow is where this gets genuinely useful: "Why did the email to jane@example.com bounce yesterday?" The agent pulls the email, reads the bounce event with the SMTP diagnostic code, checks whether the address landed on the suppression list, and explains it in plain language. That used to be five minutes of clicking through a dashboard. 1. The approval step matters more than I expected. Most MCP clients show you each tool call before it runs. For read tools that feels like friction. For send email it is exactly right. I would not connect a send-capable tool to an agent that runs unattended without scoping the key first. 2. Agents are great at chaining, bad at restraint. Ask a vague question and the agent will happily call four tools when one would do. Tight tool descriptions in the server matter as much as good prompts. 3. The server is the easy part. If your product already has a REST API, an MCP server is mostly a translation layer: tool schema in, API call out. The hard work auth, rate limits, validation already exists in the API. That is also why I prefer hosted MCP over stdio: it reuses everything the API already enforces, including that a compromised key can be revoked in one place. If you want to reproduce this end to end: grab a free SMTPfast https://smtpfa.st account 3,000 emails/month, no card , verify a domain, create an API key, and run the claude mcp add command above. The MCP docs https://smtpfa.st/docs/mcp cover the tool schemas and a few example prompts. And if you are building a dev tool yourself: ship the hosted MCP endpoint. It is a weekend of work and it makes your product usable by every AI agent your customers already run.