
Mailtea
app.mailteaPublished by mailtea.appOfficial publisherv0.10.0Updated Oct 24, 2026
Send email and newsletters with Mailtea over MCP, plus skills for email and website design.
Overview
Mailtea lets an AI assistant send and schedule email and newsletters, manage contacts, and build a publication website.
- What you can do
- Mailtea exposes 165 tools grouped into families covering email (send, batch, schedule, cancel, resend, delivery and engagement tracking, inbound mail), newsletters (draft, preview, test, schedule, send, publish, sponsor offers), templates, audience and contacts, automations, website pages and sections, sending domains and senders, analytics, and account settings. Three bundled skills guide email sending, email design, and website design. Draft requests stay drafts and do not send or publish.
- When to use it
- Useful for newsletter writers, creators and teams already sending with Mailtea who want an assistant to handle sending, scheduling, contact management and site edits conversationally, and for developers who would rather not write integration code. It does not replace Mailtea Studio or the SDKs and CLI for application code.
- Requirements
- A Mailtea account, and a verified sending domain to send. The hosted endpoint at needs no API key, no Node.js install and no code; you sign in through the browser and pick one publication and an access level. Self-hosted or local use runs the mailtea-mcp server over stdio with MAILTEA_API_TOKEN, and optionally MAILTEA_PUBLICATION_ID and MAILTEA_API_BASE_URL. JetBrains AI Assistant sends a personal access token as an Authorization header instead of browser sign-in.
Installation
In SourceWeft
- Open Mailtea in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.mailtea%2Fmailtea/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"mailtea": {
"type": "http",
"url": "https://api.mailtea.app/mcp"
}
}
}README
Mailtea Agent Plugin
Send email and newsletters. Just ask.
Mailtea lets your AI assistant send and schedule email, check delivery, write and design newsletters, manage contacts, and build your publication's website, all from a conversation. It is for newsletter writers, creators and teams who send with Mailtea, and for developers who want an agent to handle email without writing integration code.
[Get started with Mailtea: connect your account, check your setup, and send your first email.]
What you get
167 tools, grouped by what they work on:
Three skills, ready when you need them
Your assistant picks the relevant skill from your request. You can also name a skill if you want to be explicit.
[Mailtea includes email, email design, and website design skills.]
The plugin does not replace Mailtea Studio, or the SDKs and CLI for application code. Use it when an AI assistant should do the work for you.
Connect
More clients, and a one-line install for each, are under Get started.
The first time you connect, you sign in to Mailtea in your browser, pick one publication, and choose an access level from read only to full access. Your assistant can act only inside that publication at that level, and you can revoke the connection in Mailtea at any time.
Docs · Support · Privacy policy · Terms of service
Get started
You need a Mailtea account. Sending also needs a verified sending domain. The hosted connection needs no API key, no Node.js install, and no code. You sign in through your browser.
npx plugins add is the universal path. The
plugins CLI reads this package's
plugin.json and installs it into whichever agent tools it detects: Claude
Code, Cursor, Codex, Grok Build, Kimi Code, GitHub Copilot CLI, and VS Code.
Use -t <target> to pick one, and npx plugins targets to see what it found.
Then open a new session, connect Mailtea through the browser sign-in prompt, choose your publication and the access you want to grant, and paste:
Help me send my first email with Mailtea. Check my setup and guide me through anything missing.
Your agent checks the publications, senders, and domain verification available to your account, and explains the next step for anything missing. You do not need to know tool names or pick a skill.
Need an account? Start with Mailtea. Need a sending domain? Domain setup.
Manual configuration
Every entry points at the same hosted server, https://api.mailtea.app/mcp.
Unless a row above says otherwise, you sign in through your browser the first
time the client connects, and there is no key to paste.
Cline (cline_mcp_settings.json):
Zed (settings.json):
Warp (Settings, then Agents, then MCP servers):
JetBrains AI Assistant: it cannot sign in through the browser yet, so send a Mailtea personal access token (create one in Settings → API keys) as the Authorization header. Junie signs in through the browser and needs no header.
Amazon Q Developer CLI (agent configuration file), then run /mcp in a
session and open the sign-in link it prints:
Copy a prompt
Send one email. Replace the bracketed details with your own:
Send an email from [my verified sender] to [recipient]. Subject: [subject]. Message: [body].
Schedule a send:
Schedule this email for [date and time, including time zone]. Use [verified sender] and send only to [recipient].
Check delivery:
Check my recent Mailtea emails and explain any failed deliveries.
Create a newsletter draft:
Draft a newsletter for [publication] about [topic]. Give it a clear subject and one call to action. Do not send it yet.
Design your website:
Draft a home page for [publication] using its brand and existing content. Do not publish it yet.
What happens when you ask
- Draft means draft. Draft requests do not send email or publish a website.
- You choose who receives an email. Your agent asks for missing details and uses the sender, recipients, and content you supply or approve.
- An email ID means accepted, not delivered. Ask for delivery status to check the result. Do not repeat a send after a timeout until its status is known.
- Your permissions apply. The connection only reaches what your Mailtea account and the access you grant allow.
If you get stuck
Reconnecting per client
Package layout
The repository root is the plugin root. Every client loads this one directory: Agent Plugins clients (Cursor, VS Code, Kiro, Codex), Claude Code, Grok Build, and the Gemini CLI. There is no per-client subdirectory and no second copy of the skills.
That decision follows from Agent Plugins 1.0.0 §4.1: a path a client resolves
from the package must stay inside the plugin root, so a nested package cannot
share skills/ with the root by symlink or relative path. Nesting would mean
duplicating every skill. A single root keeps one copy, and the mirror's
v<version> release tag reads plugin.json at that same root.
Every manifest names the same plugin at the same version with the same
description, points at skills/ and the same MCP endpoint, and carries no
credentials. node scripts/check-manifests.mjs enforces that; the monorepo
runs it as pnpm check:agent-plugin.
Self-hosting and stdio
The hosted server at https://api.mailtea.app/mcp signs in through your
client's browser flow and stores no credentials in this package. For a
self-hosted API or local development, run the MCP server over stdio instead and
let your client inject the token:
Create a personal access token in Settings → API keys, or with
POST /v1/api-keys. Never commit one: Agent Plugins forbids credentials in
package files, and scripts/check-manifests.mjs fails the build if one appears
in an MCP header.
Versioning
There is no npm or PyPI package. The plugin is this repository, so a
release tag is
how you pin one. main always holds the latest:
Every manifest's version matches the tag, and each release's notes come from
CHANGELOG.md. Semver: a patch sharpens skill wording, a
minor adds a skill or an MCP surface, a major removes or renames one.
Authoring notes
Do not add client-only hooks, commands, or marketplace metadata to the top
level of plugin.json. Put those under a reverse-domain extensions key or in
that client's own directory, per
client extensions.
Skills here are copies of the canonical ones in the Mailtea monorepo. Edit
those, then run pnpm sync:agent-plugin-skills.
Related
- Spec: agent-plugins.org · Build a plugin
- MCP package:
mailtea-mcp - Skills-only mirror: mailtea-agent-skills
- Docs: Agent Plugin
Privacy and support
- Privacy policy: mailtea.app/privacy-policy
- Terms of service: mailtea.app/terms-of-service
- Support: [email protected]
- Docs: Agent Plugin
The plugin stores no credentials. The hosted connection signs in through your browser and reaches only the publication and access you grant, and you can revoke it in Mailtea at any time.
License
Source: README.md at commit cd95950
Tools
0Version history
3- v0.10.0LatestOct 6, 2026
- v0.9.0Oct 3, 2026
- v0.3.1Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts