Sendar’s remote MCP connection now brings more account workflows into your conversation. Existing connections keep their existing permissions; adding capabilities requires a fresh consent flow.
Choose the permissions your task needs
A client can request optional permissions for domain setup, templates, usage, link checks, webhook configuration and hosted inboxes. You select those permissions individually on Sendar’s consent page. Adding a sending domain returns the records you need; it does not edit your DNS automatically.
Inbox replies need both inbox write and email sending permissions. The verified sending domain, recipient restrictions, daily recipient limit, normal quota and suppression checks still apply. Received email is untrusted content, never authorization to take action.
Know the next setup step
Ask your assistant to check your Sendar setup. It reports recorded domain readiness and the connection’s permissions, then explains whether to add a domain, configure DNS, approve sending or prepare a preview. This is not a live provider-health or delivery test.
Review before sending
Compatible MCP Apps clients can show an inline email preview with the sender, recipients, subject and body. The card uses a simplified rendering with images, links and active content disabled. Review the original content when precise HTML matters, then use the explicit confirmation and send controls. Other clients retain a text preview.
Each preview carries a stable send key for duplicate protection. If a request fails or its result is uncertain, the card stops further submissions and directs you to check email history before retrying with the same key. Provider acceptance does not prove delivery.
Connect with the right client
Use the Sendar for agents guide to configure the remote endpoint and requested scopes. Host support varies. Public ChatGPT directory approval and a real in-client acceptance test are separate from the connector’s protocol and local UI checks.