Productivity · Remote MCP server
Mailtea
Send email and newsletters with Mailtea over MCP, plus skills for email and website design.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.mailtea/mailtea- Version
- 0.9.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- app.mailtea
- Namespace
- Namespace verified by the MCP Registry via the domain mailtea.app · how
- Listed under
- Email MCP servers
- Website
- mailtea.app
- Repository
- github.com/mailtea-app/mailtea-agent-plugin
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.mailtea.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Mailtea
Mailtea is a remote MCP server: there is nothing to install. Its endpoint is https://api.mailtea.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Mails.ai - Agent EmailA real inbox for AI agents: send, receive and thread email, behind a prompt-injection firewall. | Local · stdio |
| MailSenpaiManage MailSenpai email marketing: lists, subscribers, templates and campaigns (EU, OAuth). | Remote · HTTPLive check: sign-in required |
| MailsinkDisposable inboxes for AI agents and CI: catch the verification email, read the OTP or link. | Local · stdio |
| mailsocketEmail inboxes for AI agents: create an inbox, then block until the OTP or magic link arrives. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MailtrapSend emails and manage sending domains, suppression lists, and delivery analytics. | Local · stdio |
| MAILTYPE - Email Domain Capability IntelligenceEmail-domain intelligence: MX capability, provider, disposable status, SPF, DMARC, and MTA-STS. | Remote · HTTPLive check: sign-in required |
| MailVaktUse when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it. | Remote · HTTPLive check: ✓ handshake |
| mailverdictKeyless email checks: disposable, role, and free-provider detection, MX, and typo suggestions. | Remote · HTTPLive check: ✓ handshake |