MailLogic MCP — connect your AI assistant
Connect Claude or another compatible MCP client to MailLogic. Inspect custom-domain email configuration, manage addresses, and review delivery diagnostics using natural language.
Overview
MCP is an open protocol that lets AI applications discover and call tools from an external service. MailLogic provides a hosted server for domain email setup and management. Your assistant requests actions; MailLogic enforces account access, domain ownership, plan limits, and permissions.
The connector does not read inboxes or message bodies, send arbitrary messages, use Batch Send, or reply to conversations. It can send forwarding diagnostic emails and SMTP password-setup emails through specific tools. General sending is available separately through the MailLogic dashboard, Send API, and SMTP.
Before you connect
You need a MailLogic account and an MCP client that supports remote Streamable HTTP with OAuth. Domain setup requires a domain you control. Existing MailLogic plan limits apply; forwarding is free and paid sending starts at $4/month. Claude connector availability depends on your plan and workspace settings. Pricing
Connect
Claude
- In Claude, open Settings → Connectors → Add custom connector. Name it MailLogic and enter the server URL below.
- Add the connector and choose Connect. Sign in on the MailLogic authorization page, review the requested permissions, and approve the access you want to grant.
- Return to Claude, enable the connector for your conversation, and try the read-only setup prompt below. If more than one domain is available, specify the exact domain.
https://mcp.maillogic.io/mcpOther compatible clients
Use the same server URL, Streamable HTTP transport, and OAuth authorization. No local server installation is required. Complete sign-in in the browser; do not paste passwords or access tokens into your conversation. Client-specific menus may differ.
Permissions
Read is required; Manage is optional. The consent screen shows the permissions requested by your client. Read covers setup, usage, delivery logs, and forwarding-test results. Manage adds domain and address changes, DNS checks, SMTP credential setup, and forwarding-test creation. Grant only what you need. Tool visibility does not itself grant permission to execute it.
Review the target domain, address, and intended effect before requesting a change. Automatic DNS setup opens a separate Cloudflare approval flow. Password setup happens privately by email. Neither step is completed by the assistant on your behalf.
Tools
The current connector exposes these 13 tools. Available operations still depend on your granted scopes, account plan, and domain state.
| Tool | What it does / effects |
|---|---|
inspect_mail_setup | Read cached DNS, address, catch-all, and usage state; no changes or fresh DNS check. |
list_logs | Read one page of delivery metadata; no message bodies or new traffic. |
create_domain | Add a pending domain, or return the existing visible domain. |
check_domain_dns | Refresh and persist DNS checks; ownership and routing may change. |
begin_automatic_dns_setup | Prepare a private Cloudflare authorization link for selected DNS records; you approve in the browser. |
create_email_account | Create an address with an explicit forwarding destination. Enabling SMTP can send a private setup email. |
update_email_account | Change or clear the display name only; does not change forwarding or SMTP. |
delete_email_account | Delete an address. Routing is affected and completed batch history may be removed; catch-all stays unchanged. |
enable_smtp | Enable SMTP and request private password setup when needed; already-enabled accounts are unchanged. |
request_password_setup | Send a new password-setup email, replacing earlier usable setup links. |
set_catch_all | Enable or disable routing for unmatched addresses and optionally replace its destination. |
create_forwarding_test | Send a diagnostic email to an address’s configured destination. Requires an idempotency key. |
get_forwarding_test | Read and reconcile a test’s stored evidence; may persist status updates, but sends no email. |
Examples
Replace mail.example with a domain in your MailLogic account. These first three prompts inspect existing data without generating email traffic.
Inspect mail.example and show its cached DNS readiness and email addresses. Do not change anything.
Show my five most recent delivery-log entries. Do not generate traffic.
Check the saved catch-all configuration for mail.example without changing it.
For a setup workflow, ask: “Help me set up forwarding for mail.example. Inspect it first, explain the required changes, and ask me before applying them.” Choose the forwarding destination yourself. Any diagnostic email must use a recipient you own or have explicit permission to test.
Privacy & control
When you use a tool, its inputs and results pass through your connected AI client and its provider. Depending on the tool, results may include domain and DNS configuration, email addresses and forwarding destinations, account usage, delivery metadata, SMTP responses, and diagnostic status. The connector does not retrieve mailbox message bodies or expose SMTP passwords. Treat private DNS authorization links as sensitive.
To revoke access, open Connected Apps in your MailLogic dashboard and disconnect the client. You can also remove the connector in your AI client. Revoking access prevents future authorized use; it does not undo earlier changes or remove information already shared with the AI provider.
Troubleshooting
Cannot connect or sign in
Check the exact /mcp URL and confirm your client supports remote OAuth connectors. Sign in to MailLogic in the authorization window. Workspace administrators may need to allow custom connectors.
Permission denied or missing domain
Review Connected Apps and the consented permissions. Reconnect if you need to grant Manage. A domain that is not visible to the connection is not proof that it does not exist. Confirm the account and exact domain name.
DNS is not ready
Inspection returns cached observations. Request check_domain_dns for a fresh check; it persists results and may change ownership or routing state. DNS propagation and provider approval are separate steps. Receiving and sending readiness are checked separately.
A change timed out
Inspect the current state before retrying. For an uncertain forwarding-test creation, reuse the original idempotency key rather than starting a new test. Do not repeatedly request password-setup emails: a new link replaces earlier usable links.
A test says confirmed
Confirmed means observed acceptance by the destination SMTP server. It does not guarantee inbox placement or ongoing delivery health.
Need help?
Contact [email protected] with the tool name, time, and sanitized error details. Do not include passwords, tokens, or private authorization links.