Flinkk Mail vs AgentMail
AgentMail describes itself as an email provider built for AI agents, with a broad documented API. Flinkk Mail is an email platform with a shared team inbox that agents can work in, with a person approving what they send. This is how the two compare on what each publishes.
The main difference
AgentMail is built only for agents and documents a large tool surface. Flinkk Mail is a general email platform (sending API, shared inbox) that agents can join under a person's approval, with per-inbox permissions and an audit log.
Side by side
| Flinkk Mail | AgentMail | |
|---|---|---|
| MCP server | Hosted, eleven inbox tools, sign in with an agent key. | Hosted, 47 tools plus 2 organization tools. OAuth for Claude Desktop, Claude.ai and ChatGPT; API key header for Cursor and Windsurf. MCP docs |
| Permissions | Per agent and inbox: read, draft, send and label, draft-only or auto-send, daily limit, reply-only, allowed recipients. | Per key, scoped to an organization, pod or single inbox, as a whitelist of permissions such as message_send and draft_send. Permissions docs |
| Human approval before sending | Built in and on by default: drafts wait in an approval queue. | The permissions page does not describe a general approval step for outgoing mail. It describes an "Agent Armor" hold mode; see its permissions docs for how that applies. |
| Drafts | Yes. Agent drafts are reviewed, edited, approved or rejected in the app. | Yes. Draft tools are listed in its MCP docs. |
| Calendar | No. | Yes. Calendar tools are listed in its MCP docs. |
| Allow and block lists | Allowed recipients for sending only. No inbound lists. | Yes. List tools are listed in its MCP docs. |
| Webhooks | Signed, with retries. | Yes, on every plan. Pricing |
| Pricing | Not published yet. | Free: $0 for 3 inboxes and 3,000 emails a month, no custom domains. Developer: $20, 10 inboxes, 10 domains. Startup: $200, 150 inboxes. Pricing |
Last checked 1 November 2026. Details change, so follow the links before you decide.
Where Flinkk Mail fits
- Your team already needs a shared inbox and a sending API, and you want agents to join that inbox under a person's approval.
- Per-inbox permissions, daily send limits, reply-only mode and an audit log of every agent action are built in.
- Agent access and your day-to-day email live in one product, on your own domain.
Sources
Last checked 1 November 2026.
Give an agent an inbox
Create an agent, grant it one inbox, and keep a person in the loop for everything it sends.