ProxiedMail integration for AI agents.
ProxiedMail integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves ProxiedMail tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real ProxiedMail actions, managed and audited.
Your user connects ProxiedMail once; your agent can then create proxy-email to start your email revolution. Endless email addresses that help you to avoid your digital assets lose and boost privacy while you still using your usual email service — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants ProxiedMail access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported ProxiedMail tools.
9 tools are generated from the published ProxiedMail catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 9 tools. All published catalog entries are included in this page's server-rendered HTML.
- Auhtorization
- Auhtorization
- callback
- Create proxy-email
- Create proxy-email
- proxy-binding
- Get api token
- Get api token
- api
- Auhtorization
- Auhtorization
- callback
- List of proxy emails
- List of proxy emails
- proxy-binding
- Get received emails list by proxy email (last 55)
- Get received emails list by proxy email (last 55)
- received-email
- Get content of received email by id
- Get content of received email by id
- received-email
- Update proxy-email
- Update proxy-email
- proxy-binding
- Auhtorization
- Auhtorization
- user
ProxiedMail integration, answered
- How do AI agents use ProxiedMail through Open Connector?
- Your user connects ProxiedMail once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes ProxiedMail tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a ProxiedMail MCP server?
- Yes. Open Connector can serve ProxiedMail as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call ProxiedMail actions with credentials injected server-side.
- Where do ProxiedMail credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents ProxiedMail — keep the keys.
Open source, self-hostable, with ProxiedMail credentials that never leave your infrastructure. Run it from source today.