100% free Β· open source (AGPL)

Your mailboxes, usable everywhere β€” sequencers, AI agents, and anything that speaks email

Connect Gmail and Microsoft 365 accounts once via OAuth. OutreachEmailMCP then exposes them through SMTP, IMAP, a REST API, and MCP β€” so your outreach tools, scripts, and AI agents can send and read mail without ever touching provider passwords or OAuth themselves.

Open the dashboard β†’
Instantly / Smartlead / … ──SMTP + IMAP──▢ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” AI agents (Claude, MCP) ──────MCP──────▢ β”‚ OutreachEmailMCP β”‚ ──OAuth API──▢ Gmail Your scripts & apps ─REST+webhooks─▢ β”‚ one gateway β”‚ ──OAuth API──▢ Microsoft 365 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

How it works

1
Connect mailboxes. Click Connect (or share a signed connect-link β€” no login needed) and approve the Google/Microsoft OAuth consent. Tokens are encrypted at rest and refreshed automatically; you never handle app passwords.
2
The gateway does the plumbing. Every mailbox gets proxy-local SMTP/IMAP credentials. Outbound mail goes through a crash-safe queue and out via the provider's own API (works even where SMTP AUTH is disabled); inbound mail is indexed and served over IMAP, REST, and signed webhooks.
3
Plug anything in. Export a ready-made CSV for your sequencer, point an AI agent at the /mcp endpoint with a permission-scoped API key, or use plain SMTP/IMAP/REST from any tool ever written.

Why a gateway?

Providers killed passwords

Google and Microsoft removed basic authentication β€” the username+password login every sequencer and legacy tool depends on. OutreachEmailMCP restores that interface locally while speaking modern OAuth to the providers, so nothing breaks and nothing violates their auth requirements.

Sequencers AND direct access

One connection serves both worlds: bulk-import your accounts into Instantly, Smartlead, Lemlist and friends via CSV β€” and simultaneously read replies or send from your own code, no double setup.

Built for AI agents

The MCP endpoint gives agents typed tools β€” list accounts, send email, read inboxes, check delivery status β€” behind API keys with granular permissions (send-only keys, read-only keys). Your agent never sees a mailbox credential.

Reliability included

Persistent send queue with retries and backoff, per-message delivery log, automatic token refresh, accounts pause (never lose mail) when re-authentication is needed.

Who it's for

Outreach & growth teams

Manage dozens of sending mailboxes and move them between sequencers with a CSV export instead of re-doing OAuth in every tool.

Developers & agencies

One REST/webhook API for sending and reading across Gmail and Microsoft, self-hosted next to your stack in a single Docker container.

AI builders

Give agents safe, scoped email abilities over MCP without embedding provider OAuth flows into every project.

Works with

InstantlySmartleadLemlistReply.ioWoodpeckerClaude / MCP clientsAnything with SMTP or IMAP

Completely free

OutreachEmailMCP is free to use and AGPL-licensed open source β€” self-host it with one docker compose up, inspect every line, or use this hosted instance at no cost.

Open the dashboard β†’