MAILMAN MCP / YOUR AI POSTAL SYSTEMMAILMAN MCP / MAIL

Your email stays under your control.

Understand what MailMan can access, where the boundaries are, and how to disconnect.

Source-based access flow. MailMan processes requested mail and stores account, security and operation records. Your chosen AI client and any configured authorization transport have separate processing policies.

01MAILMAN / MAIL

What we access

Tools process the messages, metadata and attachments requested in authorized accounts. Read and Write are separate application permissions; provider grants can further restrict capabilities.

02MAILMAN / MAIL

What is stored

The implementation stores product identities, account settings, encrypted provider credentials, operation metadata, selected IDs, sender summaries and some operation results, including send-recipient metadata. Optional Composio transport depends on operator configuration. Requested mail content passes through tool results to your chosen client. Local CLI plans and journals may retain selected message information. These local files are not encrypted by the CLI.

03MAILMAN / MAIL

Who can act

The authenticated product user must own the account. Account status, read/write access and provider capabilities are checked before operations. A mailbox connection does not grant a shared customer workspace or team access.

04MAILMAN / MAIL

Approval guarantees and exceptions

Supported CLI routines use a frozen selection and exact digest approval. General write-enabled MCP tools can modify or send without a separate MailMan approval dialog. Your AI client's confirmation policy is a separate control.

05MAILMAN / MAIL

Disconnect and revoke

Disconnect removes stored mailbox credentials, marks the connection revoked and cancels queued work. This does not remove the provider-side grant. Revoke that grant or app password in the provider's settings. Revoke personal access tokens separately in Connections.

06MAILMAN / MAIL

Errors and partial results

Inspect per-account failures. Provider-accepted sending is not proof of delivery. When the outcome is unknown, check the provider before retrying; never count it as completed.

07MAILMAN / MAIL

Retention and incident contact

Andrew Naegele is the support and privacy contact: [email protected]. For billing questions, use [email protected]. Read the privacy notice for retention defaults, service providers and deletion limits. No certification or unverified operational encryption claim is made.

MAILMAN / MAIL