Add Mailzzy's MCP server to Gemini CLI and check campaigns, manage contacts and send transactional emails without leaving your terminal.
Works via MCP
One settings.json entry
OAuth sign-in
Built for developers
One config entry, one sign-in, and you're ready.
Add the Mailzzy MCP server URL to ~/.gemini/settings.json under mcpServers.
Restart Gemini CLI and complete the Mailzzy sign-in when prompted.
Try “Show me my recent campaigns.”
Get answers and make changes without opening the dashboard.
Answers without the dashboard
Keep data tidy as you build
Previewed, then confirmed
A few things developers ask Gemini CLI to do in Mailzzy.
You ask “Did the reset email to sam@example.com bounce?”
Gemini CLI checks delivery events
You ask “Create 10 test contacts in a QA group.”
Contacts are bulk-created
You ask for opens and clicks on today's update
Gemini CLI pulls the campaign report
You ask “Export the trial-users segment.”
Gemini CLI returns a CSV link
You ask to email the invoice to finance@example.com
A transactional email is sent
You ask “Which sending domains are verified?”
Gemini CLI lists your sending domains
Everything you need to know about using Mailzzy from your terminal.
Mailzzy currently documents Gemini CLI. Other MCP-compatible tools, such as Cursor and VS Code, use the same server.
No. You authorize with OAuth 2.1 + PKCE when Gemini CLI first connects.
No. Sends and deletions show a preview and need your confirmation.
On the Mailzzy Docs page.
It's currently in beta.
Yes. For scripted integrations, use the Mailzzy API.
Let's keep in touch
Sign up for our weekly email marketing newsletter and Mailzzy updates.
For more details, review our Privacy Policy