Truncus Mcp Server
Send transactional email from your coding agent via Truncus, with validation, delivery tracking, and domain management.
Overview
io.github.codevanmoose/truncus-mcp-server is a Grow-phase MCP server that lets coding agents send transactional email through Truncus with validation, tracking, and domain management.
What is this MCP server?
- Stdio MCP @truncus/mcp-server v0.1.3 with TRUNCUS_API_KEY
- Send transactional email from AI agents with Truncus delivery pipeline
- Validate messages and track delivery status from agent workflows
- Manage sending domains via Truncus dashboard-linked API
- Purpose-built for agent-driven email, not marketing automation suites
- Package @truncus/mcp-server version 0.1.3
- Required secret TRUNCUS_API_KEY environment variable
- Capabilities listed: send transactional email, validate, track delivery, manage domains
What problem does it solve?
You need transactional email in agent workflows but lack a simple MCP surface for send, validate, and domain setup on Truncus.
Who is it for?
Indie SaaS builders using Truncus who want password-reset, receipt, and alert email callable from Claude Code or Cursor.
Skip if: Teams needing bulk marketing automation, a different ESP with no Truncus account, or flows that cannot use a third-party transactional API key locally.
What do I get? / Deliverables
Once TRUNCUS_API_KEY is set, your agent can use Truncus MCP tools to send transactional mail and monitor delivery without custom SDK wiring each time.
- Agent-accessible Truncus send and validation workflows
- Delivery tracking and domain management via MCP tools
- npm-published server v0.1.3 with stdio transport
Recommended MCP Servers
Journey fit
Transactional email MCP fits Grow lifecycle—the phase where solo builders wire onboarding, receipts, and password resets into live user journeys. Truncus handles outbound lifecycle email infrastructure; the canonical shelf is lifecycle comms rather than frontend UI or SEO.
How it compares
Truncus transactional-email MCP connector, not an SEO or newsletter-content agent skill.
Common Questions / FAQ
Who is io.github.codevanmoose/truncus-mcp-server for?
Solo builders and small teams on Truncus who use MCP agents and need transactional email, validation, and domain tools in the IDE.
When should I use io.github.codevanmoose/truncus-mcp-server?
Use it in Grow lifecycle work—or late Build when wiring auth and notifications—when agents should send or test transactional email via Truncus.
How do I add io.github.codevanmoose/truncus-mcp-server to my agent?
Install @truncus/mcp-server from npm, set TRUNCUS_API_KEY from truncus.co/dashboard/settings/api-keys, and add the stdio server to your MCP client configuration.