Mcp Server
Let your coding agent send and validate transactional email through Truncus while you implement onboarding, receipts, and alerts without leaving the editor.
Overview
Truncus MCP Server is a MCP server for the Grow phase that lets AI agents send transactional email, validate messages, track delivery, and manage domains via Truncus.
What is this MCP server?
- npm package @truncus/mcp-server v0.1.1 with stdio transport
- Requires TRUNCUS_API_KEY from truncus.co/dashboard/settings/api-keys
- Send transactional email, validate messages, track delivery, and manage domains from the agent
- Open-source repo github.com/vanmoose/truncus-mcp-server
- Purpose-built for AI agents, not bulk newsletter campaigns alone
- Package version 0.1.1
- Transport: stdio
- npm identifier @truncus/mcp-server
What problem does it solve?
You waste cycles context-switching to email dashboards and curl tests whenever your agent implements lifecycle email without a first-class provider integration.
Who is it for?
Solo SaaS builders who want agent-driven implementation of transactional email with validation and delivery visibility through Truncus.
Skip if: Builders who only need cold outreach lists, in-app chat, or email with no third-party API budget or Truncus account.
What do I get? / Deliverables
With TRUNCUS_API_KEY configured and the stdio server registered, your agent can send and monitor transactional email while you ship onboarding and notification features.
- Local stdio MCP server wired to Truncus
- Agent-accessible send, validate, delivery track, and domain management operations
Recommended MCP Servers
Journey fit
Transactional email is how users experience your product after launch, so the canonical shelf is Grow where lifecycle messaging and delivery health live. Truncus focuses on send, validate, track delivery, and domain management—classic lifecycle operations rather than one-off marketing copy.
How it compares
Transactional email MCP bridge via npm stdio, not a copywriting skill or a hosted-only ads analytics server.
Common Questions / FAQ
Who is co.truncus/mcp-server for?
Indie developers and agent users shipping SaaS or tools that need reliable transactional email during grow-phase user lifecycle work.
When should I use co.truncus/mcp-server?
Use it when you are implementing or debugging transactional sends—welcome mail, receipts, alerts—and want the agent to call Truncus for validate, send, and delivery tracking.
How do I add co.truncus/mcp-server to my agent?
Install @truncus/mcp-server from npm, set TRUNCUS_API_KEY in the environment, and register the stdio MCP server in Claude Code, Cursor, or your client's MCP config.