Connect your AI agent to live email operations. Keep the same identity and permissions.
One endpoint, discovered automatically. Your client authorizes in the browser over OAuth 2.1, or a headless caller uses the same scoped key the REST API already takes.
✓Full MCP on every tier, including free. It burns no credits.
Tools with product meaning
Operator prompt
Inspect the onboarding flow, explain where contacts stop, and show the evidence before proposing a change.
Discover
email_* tools
Inspect
Company context
Propose
Controlled write
[ 01 / 03 ]What the connection gives you
The product's own operations, not a side channel.
Connect once
No transport-specific token to mint, store, rotate, or leak.
Inspect and prepare work
Read live context, analyse results, and assemble the exact change before making it.
Keep consequential writes explicit
Risky calls demand a confirmation the client cannot talk its way around.
[ 02 / 03 ]Why it holds up
The transport does not decide authority.
MCP exposes the surface. The credential still says who is acting, which company they can reach, and what they're allowed to do — and an agent driving a tool is not an operator at a keyboard.
- OAuth 2.1 acts as the signed-in human, and revocation is checked on every call.
- A first-party API key pins a headless caller to a ranked scope and one company.
- Revoking a key stops REST and MCP together — there is no second credential to forget.
- The gate sits on the action itself, never on the client that asked for it.
Tools with product meaning
Operator prompt
Inspect the onboarding flow, explain where contacts stop, and show the evidence before proposing a change.
Discover
email_* tools
Inspect
Company context
Propose
Controlled write
[ 03 / 03 ]Related
Connect the client you already use
Questions people ask us
Give your agent live context in one connection.
Connect your client, read your live sending state, then make one controlled write.