Drin connects to Cursor over MCP, so the agent in your editor can scaffold a send, fire a test, verify a domain and inspect inbound mail — all of the 54 tools, right next to the code you're writing.
// .cursor/mcp.json — illustration; exact setup in the docs { "mcpServers": { "drin": { "command": "npx", "args": ["@drin00/mcp"], "env": { "DRIN_API_KEY": "drin_live_…" } } } } # In Cursor's chat, with the project open: > Wire the signup flow to send a welcome email via Drin, > then send me a test to confirm it works.
Mint a scoped key in the dashboard. Keep it in your environment, not in source — the config reads it from DRIN_API_KEY.
Add Drin to your .cursor/mcp.json (or Cursor's MCP settings). The 54 tools appear once Cursor reloads.
Ask Cursor to add a send to a route, then send a test to confirm — it calls Drin directly instead of guessing at an SDK.
Ask Cursor to add a Drin send call to a route or job, generate the typed client code, and wire your key from env.
Fire a real test message through the MCP tools to confirm the integration works — without switching to a terminal.
Pull the SPF, DKIM and DMARC records into the editor, drop them in your DNS notes, and confirm verification.
List threads and inspect a message right in chat, so you can build and debug inbound handling against real mail.
Grab a key, add Drin to your MCP config, and let the editor send and test for you. Test in the sandbox; production starts at $3 a month.