Run tinyEmail
just by asking.
Connect Claude or ChatGPT to tinyEmail with the new MCP Server — and create campaigns, manage audiences, and configure senders in plain language. No dashboards. No tab-switching.
Works with Claude & ChatGPT · X-API-Key auth · Key never stored
X-API-Key
Never stored
0
dashboards opened
Works where you already work
Your work lives in your assistant.
Now your email does too.
Marketers lose hours bouncing between an AI assistant and a marketing dashboard. The MCP Server closes that gap.
Endless context-switching
You plan in your AI assistant, then re-do it all by hand in a separate dashboard. Every tab switch is lost momentum.
Manual, repetitive setup
Segmenting an audience, drafting a campaign, verifying a sender — the same clicks, over and over, for every send.
The MCP Server fix
Your assistant talks straight to tinyEmail. Describe what you want; it runs the whole workflow end to end.
Three ways to connect
Set up once. Then just ask.
Point your AI client at the hosted endpoint, authenticate with your API key, and tinyEmail tools appear right in your chat.
https://mcp.tinyemail.com/mcp
Claude Code
Add the server to ~/.claude/settings.json and issue commands right in your terminal.
$ claude
> List all my campaigns
✓ 12 campaigns found
Claude Desktop
Bridge to the server via claude_desktop_config.json. tinyEmail tools appear under the tool picker.
ChatGPT
Connect through OpenAI's GPT Actions pointed at the tinyEmail REST API with API-key auth — no native MCP required.
# custom GPT
auth: X-API-Key
→ tinyEmail REST API
Your whole workflow, in plain language
Everything you'd click through in the dashboard, your assistant can now do for you — just by asking.
Campaigns
Create, edit, schedule, and pause campaigns. “Pause anything under 20% open rate.”
Audiences
Segment, import, and clean lists on command. “Build a segment of lapsed buyers.”
Senders
Add and verify sending identities without leaving the chat. “Verify my new domain.”
Automation
Chain steps into one request and let your assistant run them end to end — no copy-paste.
Your key is yours. Full stop.
The MCP Server is a thin, secure bridge — not a vault. Your API key passes straight from your AI client to the tinyEmail API and is never stored or logged.
-
Direct transmission. Authenticated via the X-API-Key header, client → API.
-
Zero retention. The server never persists or logs your key.
-
Hosted & managed. A maintained endpoint with no infrastructure for you to run.
Frequently asked questions
What is the tinyEmail MCP Server?+
It's a hosted Model Context Protocol integration that acts as a secure bridge between AI assistants and the tinyEmail API. Enterprise customers can manage campaigns, audiences, and senders using plain natural language inside their preferred assistant.
Which AI assistants are supported?+
Claude Code (CLI), Claude Desktop, and ChatGPT. Claude clients connect natively over MCP; ChatGPT connects through OpenAI's GPT Actions pointed at the tinyEmail REST API — no native MCP protocol required.
Is my API key secure?+
Yes. Your key is sent in the X-API-Key header directly from your AI client to the tinyEmail API. The MCP Server never stores or logs it.
Do I need to write code?+
No. Setup is a one-time configuration in your AI client. After that you issue plain-language commands like “List all my campaigns” — no scripting required.
Who can use the MCP Server?+
The MCP Server is available to tinyEmail Enterprise customers. Reach out to your account team if you'd like it enabled.
Stop clicking. Start asking.
Connect your assistant to tinyEmail and run your entire workflow in plain language.
Enterprise · Hosted & managed · API key never stored
Live product demo · the MCP Server in action
.svg)
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
