Mailzzy

What Mailzzy MCP server does

Mailzzy MCP server exposes Mailzzy email marketing and CRM operations to compatible AI clients. It provides 49 tools for working with campaigns, audiences, contacts, segments, templates, automation workflows, transactional messages, and performance data.

Campaign workflows can include drafting or updating a message, sending a test, checking recipient counts and sending limits, sending immediately, scheduling delivery, and cancelling a scheduled campaign. Audience operations support groups, segments, and tags, including de-duplicated recipient counts. Contact tools cover creation, updates, tagging, grouping, archiving, CSV import, and CSV export for a segment or group.

The Mailzzy MCP server also supports saved segment filters, template and automation editing, one-to-one transactional email, delivery logs, campaign metrics, date-range performance, and domain-level deliverability reporting.

How it works

The service is hosted at https://api.mailzzy.com/crm/mcp/ and uses Streamable HTTP. No local package or process is required. An MCP client connects to the endpoint and completes OAuth 2.1 authentication with PKCE and dynamic client registration.

Sign-in occurs on Mailzzy's login page, so the client does not receive the user's password. The client receives a short-lived token scoped to the connected Mailzzy account. Tool calls can use the advertised mcp:read, mcp:write, and mcp:send scopes, and account data is restricted to the authenticated user's account.

Read-only tools are annotated as such. Actions including campaign sending, transactional email, contact deletion, and cancellation of a campaign are marked destructive, allowing clients that honor MCP annotations to request confirmation before execution.

Setup and configuration

Create or use a Mailzzy account, then add the hosted endpoint to an MCP client. Claude can add it as a custom connector, while Claude Code can use:

claude mcp add --transport http mailzzy https://api.mailzzy.com/crm/mcp/

Cursor and VS Code use their MCP configuration files with the same URL. Cline can add it under remote MCP servers with Streamable HTTP selected. After adding the connection, authenticate in the browser when prompted. Claude Code completes authentication through /mcp; Cline may require removing and re-adding the server if authentication must be restarted.

Clients that implement the MCP authorization specification can use the endpoint directly. Unauthenticated requests receive 401 and a WWW-Authenticate header containing protected-resource metadata for authorization discovery. No environment variables or local server installation are required.

Tools and capabilities

The Mailzzy MCP server includes tools for:

• Drafting, updating, testing, sending, scheduling, and cancelling campaigns
• Selecting recipients through groups, segments, and tags
• Checking de-duplicated audience sizes and daily or monthly sending limits
• Creating, updating, tagging, grouping, archiving, importing, and exporting contacts
• Building and previewing saved contact segments
• Creating and editing templates and automation workflows
• Sending individual transactional emails and reading delivery logs
• Reviewing campaign results, date-range performance, and recipient-domain deliverability

Limitations and notes

A Mailzzy account is required. The repository contains documentation and a registry manifest; the hosted service is operated by SoftSages and is not open source. Access is account-scoped, and the available actions depend on the OAuth scopes granted to the client.

Removing the connector from the MCP client disconnects the account. Developers should also account for confirmation behavior around destructive operations, since client support for MCP annotations determines whether a confirmation prompt appears.