Enable local access

  1. Open Settings → App Preference → MCP Access. It is off by default and separate from the built-in AI Provider switch.
  2. Enable access, then copy the displayed loopback URL and connection token. In a compatible AI client on the same computer, add an HTTP/Streamable HTTP MCP server called AeroMailer using that URL and private bearer token. Use the app’s MCP setup guide for client-specific configuration.
  3. Keep AeroMailer open or in the tray. The service is local, not a public URL; never expose it to the network or commit the token to a project.
AeroMailer interface: Connect a local AI client through MCP
Sample-data app screenshot. Select the image to view it at full size; your accounts and content will differ.

Review proposed changes inside AeroMailer

A connected client can read only supported workspace data and propose supported actions. Open MCP approval queue to review the exact request before approving or rejecting it. Confirming in AI chat is not approval in AeroMailer. Do not approve an action you did not ask for. An interrupted send or other uncertain outcome must be verified before any retry.

Turn access off when finished

Disable MCP access to revoke that connection channel, or replace the token if it is lost or exposed. This does not undo completed actions or erase data already shared with a client. Tokens and pending approvals are local device permissions; they do not transfer with a workspace. This is different from the in-app AI Assistant.