Connect MailSend to AI with MCP
Connect a compatible AI client to MailSend using the hosted MCP endpoint and secure OAuth authorization.
Docs Summary
- What this page explains: Connecting compatible AI clients to MailSend through OAuth and the hosted MCP endpoint.
- Who should use it: MailSend users and developers who want controlled AI-assisted email operations.
- Related MailSend feature: Remote MCP tools, OAuth grants, quota and policy enforcement
- Common use cases: Sending transactional emails, checking delivery status, managing templates, and reviewing usage
- Related docs: API Keys & Authentication, Email API, Templates, Billing & Plans
MailSend MCP lets compatible AI assistants read MailSend data and perform explicitly approved email operations in your workspace. Use the hosted connection URL below; you do not need to create an API key or manually copy an OAuth access token.
https://mailsend.dev/mcpOnly connect MailSend through a trusted MCP client. Never paste an access token into a chat, URL, browser extension, or third-party form.
Connect your MCP client
Do not open the MCP URL or OAuth endpoints directly in a browser. Open your AI client's connectors or MCP settings, choose to add a remote MCP server, and enter https://mailsend.dev/mcp. The client discovers MailSend's OAuth endpoints and generates the required client identity, callback, state, resource, and PKCE values. It then opens MailSend for you to sign in, select the intended workspace, review permissions, and approve the connection.
The authorization screen must be hosted on mailsend.dev. If a client asks you to paste a MailSend API key instead, stop and do not continue.
How OAuth protects your account
OAuth gives the connected client a short-lived, workspace-bound token instead of your password or API key. Access is limited to the permissions you approve. MailSend rechecks workspace membership, role eligibility, quotas, suppressions, verified senders, verified domains, and platform safety controls on every operation.
Available permissions
| Permission | What it allows |
|---|---|
| emails:send | Send a transactional email through MailSend's normal quota, suppression, sender, and domain checks. |
| emails:read | Read email details and delivery status for the authorized workspace. |
| templates:read | Read saved templates and immutable template versions. |
| templates:write | Create, update, duplicate, archive, and restore workspace templates. |
| domains:read | List sending domains and read their verification status. |
| domains:write | Manage workspace sending domains and their DNS verification workflow. |
| usage:read | Read current workspace usage and quota information. |
| contacts:read | Read workspace contact lists and contacts. |
| contacts:write | Create, update, move, and delete workspace contacts and lists. |
| contacts:export | Export a bounded, CSV-safe contact list. |
| campaign.read | Read campaign drafts, progress, and delivery outcomes. |
| campaign.write | Create campaign drafts and immutable approval snapshots. |
| campaign.send | Test, launch, pause, cancel, or safely retry approved campaigns. |
| audience.read | Read workspace audiences and their contacts. |
| audience.write | Create audiences and manage their contacts. |
| segments:read | Read and preview workspace segments. |
| segments:write | Create and delete workspace segments. |
| analytics:read | Read aggregate workspace sending and deliverability analytics. |
| recipients:verify | Check recipient syntax, mail routing, risk, and available mailbox signals. |
Available tools
Full access enables the reviewed MailSend email, template, domain, usage, contact, campaign, audience, segment, analytics, and recipient-verification tools in the selected workspace, subject to the user's current workspace role. It does not include billing, API-key management, team or member management, workspace administration, platform administration, infrastructure controls, raw credentials, or secret access.
Sending and quota safeguards
MCP sends use the same protected delivery path as the MailSend application. Each direct send is limited to 10 unique recipients, requires approval of the exact preview, and enforces verified senders, suppressions, quota, rate limits, and idempotency. Marketing uses approved campaign snapshots; multiple distinct transactional messages use durable asynchronous batch jobs.
When you provide recipients and a topic, ChatGPT generates the complete subject, responsive HTML, and plain-text fallback before preview. Supported clients visibly render that exact email with prefilled sender and recipients; approve and choose Send email immediately, or choose Edit to revise the existing values and approve the regenerated preview.
Disconnect or revoke access
Open MailSend Settings and go to Connected Apps. Find the MCP client and choose Revoke. Revocation invalidates the grant and its access and refresh tokens. You can reconnect later through the same OAuth flow.
Troubleshooting
If the client cannot connect, confirm that the server URL is exactly https://mailsend.dev/mcp and that pop-ups are allowed for the sign-in flow. Do not manually visit /oauth/authorize or /oauth/token: the first requires a complete authorization request from a client and the second accepts only a form-encoded POST. If authorization fails inside the client-driven flow, confirm that you are signed in to MailSend, still belong to the selected workspace, and have the role required for the requested permission. Revoke the connection in Connected Apps and reconnect if the client has stale credentials.
For MCP client developers
MailSend implements Streamable HTTP and OAuth discovery. Clients should discover protected-resource and authorization-server metadata, use Authorization Code with PKCE (S256), include the MailSend resource indicator in authorization and token requests, and send the resulting bearer token in the Authorization header. Do not place bearer tokens in query parameters.
https://mailsend.dev/.well-known/oauth-protected-resource
https://mailsend.dev/.well-known/oauth-authorization-server