Manage Subscribers, Broadcasts, Sequences, Automations, and reporting in Mailrith.
This public repository contains the versioned developer surfaces for building safe AI agent email marketing workflows with Mailrith:
The hosted Mailrith application and its private infrastructure remain in a separate private repository. This repository intentionally contains no application source, database migrations, deployment credentials, customer data, or private operational configuration.
Requirements: Node.js 20 or newer, pnpm 11.7.0, and Python 3.10 or newer.
pnpm install --frozen-lockfile
pnpm validate
Generated SDK and MCP files come from packages/public-api. Change the public contract first, then run:
pnpm generate:agent-artifacts
pnpm generate:agent-integrations
pnpm agent:release:manifest
Commit the contract and every regenerated artifact in the same change.
The Release Agent Packages workflow prepares checksummed npm, Python, and
platform packages on coordinated runs. The prepare-cli and cli targets
prepare only the CLI archive. Publishing requires the protected
agent-packages-production environment and trusted publishing configured for
npm and PyPI. A matching agent-v<version> tag or an explicitly approved
publish run starts publication.
The CLI, other npm packages, Python, and marketplace submission versions advance independently through the coordinated workflow. This keeps already-submitted marketplace archives unchanged while another package channel receives a compatible patch release. The release manifest records each version, the contract digest, package digests, and public-registry status.
The platform archives are submission-ready files for OpenAI, Claude, Cursor, Gemini CLI, GitHub Copilot CLI, Microsoft, and Cline. Provider review and public directory approval are separate from npm and PyPI publication.
CLI 1.1.2 was published to npm on September 4, 2026. The other packages and prepared
marketplace artifacts remain at 1.1.1. See Releasing The CLI
for the separate CLI version fields and the preparation and publication steps.
Do not report security vulnerabilities in public issues. Follow SECURITY.md.
Forking the code is allowed. Modified public versions must use distinct names and clearly say that they are unofficial and not affiliated with Mailrith. See the Mailrith Trademark And Unofficial Fork Policy.
The code is available under the MIT License. Mailrith brand identifiers are not licensed with the code.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @mailrith/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-mailrith-mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@mailrith/mcp-servernpmMailrith Email Marketing works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.