Manage subscribers, broadcasts, sequences, automations, and reporting within the Mailrith email marketing platform.
Also known as anrawool/mailrith-agent-platform, mailrith, @mailrith/mcp-server
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- 771
- Latest version
- 2.0.1
- Last commit
- Nov 11, 2026
- License
- MIT
What is Mailrith MCP?
Mailrith manages subscribers, broadcasts, sequences, automations, and reporting within the Mailrith email marketing platform.
Summary generated from the project's README
About Mailrith MCP server
Mailrith Email Marketing provides an interface for managing email marketing operations through an MCP server. Developers and users can interact with subscribers, broadcasts, sequences, and automations. The server supports both remote connections via a hosted endpoint at api.mailrith.com/mcp and local installations using stdio or self-hosted HTTP transports. Remote clients like Claude Desktop connect using Mailrith OAuth, while local stdio setups require a workspace API key provided through the MAILRITH_API_KEY environment variable.
This server offers different compatibility profiles including submitted, compact, and custom. The submitted profile is designed for general-purpose agents and includes tools like subscribers_list, broadcasts_create, and broadcasts_schedule. It enforces strict permission checks based on the user's granted OAuth scopes or workspace API key. The system ensures security by redacting sensitive webhook tokens during automation reads and rejecting credentials passed as command arguments to prevent exposure in shell history.
What you can do with it
- 1Manage email subscriber listsAsk the AI to retrieve or view your current list of email subscribers.
- 2Schedule marketing broadcastsInstruct the agent to prepare and schedule a new email broadcast for a specific time.
- 3Update automation statusesHave the client modify the status of existing email automations or sequences.
- 4Perform broadcast preflight checksUse the agent to validate a broadcast before it is officially sent to recipients.
Written from the project's README. Every use case is checked against a quote from it.
How to install Mailrith MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Mailrith MCP in Claude Code
$ claude mcp add --env 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' mailrith -- npx -y @mailrith/mcp-serverInstall Mailrith MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Install Mailrith MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mailrith": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Install Mailrith MCP in VS Code CLI
$ code --add-mcp '{"name":"mailrith","type":"stdio","command":"npx","args":["-y","@mailrith/mcp-server"],"env":{"MAILRITH_API_KEY":"<YOUR_MAILRITH_API_KEY>"}}'Install Mailrith MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Install Mailrith MCP in Codex
$ codex mcp add mailrith --env 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' -- npx -y @mailrith/mcp-serverInstall Mailrith MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mailrith] command = "npx" args = ["-y", "@mailrith/mcp-server"] [mcp_servers.mailrith.env] MAILRITH_API_KEY = "<YOUR_MAILRITH_API_KEY>"
Install Mailrith MCP in Gemini CLI
$ gemini mcp add -s user -e 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' mailrith npx -- -y @mailrith/mcp-serverInstall Mailrith MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mailrith": {
"command": "npx",
"args": [
"-y",
"@mailrith/mcp-server"
],
"env": {
"MAILRITH_API_KEY": "<YOUR_MAILRITH_API_KEY>"
}
}
}
}Configuration
MAILRITH_API_KEYRequiredSecretA Mailrith workspace API key.
| Name | Description | |
|---|---|---|
| MAILRITH_API_KEY | A Mailrith workspace API key. | RequiredSecret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableanrawool/mailrith-agent-platform is public and reachablegithub.com/anrawool/mailrith-agent-platform ↗Pass
- Package names this repository as its source@mailrith/mcp-server names anrawool/mailrith-agent-platform as sourcenpmjs.com/package/@mailrith/mcp-server ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @mailrith/mcp-servernpmjs.com/package/@mailrith/mcp-server/v/2.0.1#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/anrawool/mailrith-agent-platform ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @mailrith/mcp-serverPass
- No critical advisory in the package or its dependencies101 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 98 msPass
README
View on GitHubMailrith MCP Server
Official MCP server for Mailrith.
The server uses the stable @modelcontextprotocol/sdk package for hosted and
stdio transports while preserving Mailrith's generated operation schemas.
Use the remote MCP endpoint at https://api.mailrith.com/mcp for hosted agent
integrations, or run the local server from this repo for stdio or self-hosted HTTP use.
Claude Desktop and other user-connected remote MCP clients authenticate through
Mailrith OAuth. Code-first clients that can safely store credentials may send a
workspace API key or OAuth access token as Authorization: Bearer <credential>.
Official MCP Registry
The registry metadata in server.json identifies the server as
com.mailrith/mailrith. Clients can use the canonical Streamable HTTP endpoint
at https://api.mailrith.com/mcp, which authenticates through OAuth, or install
the local stdio package from npm. Local installs require a workspace API key in
MAILRITH_API_KEY.
The hosted server requests Full Email Marketing Access by default for a
general-purpose agent. It covers every public email-marketing operation in the
selected workspace, but not billing, team, account-security,
credential-reading, or internal administration. The
discovery_get_capabilities connection check requests the complete public
permission catalog so Mailrith can show every Work Profile and default to Full
Email Marketing Access. The user can choose Reporting, another focused Work
Profile, or custom permissions instead. OAuth stores only the permissions the
user approves, and every tool checks those permissions again when it runs.
MAILRITH_API_KEY="<secret>" pnpm --filter @mailrith/mcp-server exec tsx src/cli.ts --transport stdio
Local stdio reads MAILRITH_API_KEY from the client secret environment. The
server rejects credentials passed as command arguments so they do not appear in
process listings or shell history. Local stdio stops with a clear setup error
when the environment variable is missing because it has no browser-based OAuth
flow.
Self-hosted HTTP does not read a process-wide API key. Each client must send its
own workspace API key or OAuth access token in the Authorization header. The
built-in HTTP listener accepts only 127.0.0.1 or localhost; put a TLS reverse
proxy in front of it when another machine needs access.
The default submitted profile exposes a fixed reviewed catalog of focused
tools such as:
subscribers_listbroadcasts_createbroadcasts_preflightbroadcasts_schedulebroadcasts_sendsequences_update_statusautomations_update_status
Every submitted tool has a human-readable top-level title and
annotations.title, a narrow description, exact input and output schemas,
explicit safety annotations, and machine-readable operation permissions.
Request-body inputs expose their JSON type directly as well as their exact
referenced schema so connector review tools can validate them without expanding
$ref values first. Tools other than the connection check advertise their
exact OAuth permissions. The connection check advertises the complete
permission catalog so OAuth can offer every Work Profile; its result still
reports the exact permissions granted to the connection. The catalog stays the
same for every user so clients can review and select tools reliably. Workspace
role, plan, product readiness, and granted permissions are enforced when a tool
runs.
Anonymous clients may initialize and list this static catalog so ChatGPT and
other hosts can start OAuth linking. Anonymous tool calls never reach the
Mailrith product API and return HTTP 401 with a standards-based
WWW-Authenticate challenge instead. Authenticated calls that need more
permissions return HTTP 403 with the complete replacement permission set.
Single-tool responses also include MCP's tool-level OAuth challenge metadata
for clients that use it when linking or reconnecting an account.
Each anonymous HTTP request accepts one JSON-RPC message. Authenticated
requests may batch up to 25 messages. These limits keep discovery and tool
responses predictable for every connected workspace.
Automation reads never return saved webhook bearer tokens or custom header values. They return only whether each value is configured. If a client reads an Automation and sends the redacted definition back during an update, Mailrith preserves the existing values unless the client explicitly replaces or removes them. Changing the webhook destination requires new credential values so an old secret cannot be carried to another service.
The package also preserves two explicit compatibility profiles:
compactexposes the earlier seven discovery and routing tools.customexposes generated focused tools with caller-selected Work Profile, permission, and read-only filters.
Use these profiles only for local or purpose-built clients. The public ChatGPT/Codex plugin
and the Claude Connector use the fixed submitted profile at the single /mcp
endpoint.
Official Builds And Forks
Modified public versions must use distinct package, registry, plugin, and service names and clearly say that they are unofficial. See the Mailrith Trademark And Unofficial Fork Policy.
Mailrith MCP questions
How do I add Mailrith MCP to Claude Code?
Run claude mcp add --env 'MAILRITH_API_KEY=<YOUR_MAILRITH_API_KEY>' mailrith -- npx -y @mailrith/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Mailrith MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I authenticate with the Mailrith MCP server?
Claude Desktop and other remote clients use Mailrith OAuth, while code-first clients can use a workspace API key or OAuth access token in the Authorization header.
What tools are available in the default profile?
The default 'submitted' profile includes tools for managing subscribers, creating and scheduling broadcasts, and updating the status of sequences and automations.