Connect OpenCode to ProxiedMail
Set up in minutes
Choose where it runs
On your computer through your own OpenCode, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in ProxiedMail
A preset of real ProxiedMail operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect ProxiedMail
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your OpenCode first calls in. opencode mcp add only saves the config. OpenCode connects when it starts — run opencode, or restart a running one.
1. Run this in your terminal
2. Choose Remote and paste your server URL
3. Choose No when asked about OAuth authentication — the link itself is the key
<your-link> is your personal server URL — setup mints it for you.
Tools OpenCode gets
ProxiedMail
10 toolsList the account's proxy email addresses and usage metadata.
Create an alias forwarding to the supplied real email addresses.
Change selected alias settings; omitted fields are preserved.
Replace the forwarding destinations and their enabled flags.
Set the URL receiving incoming-email webhooks.
Enable browsing received email through the API.
Disable API browsing of received mail for this alias.
Read the last 55 received messages for a browsable alias.
Read one received message's payload and attachment links.
Read the payload captured by an existing webhook receiver hash.
About OpenCode
Frequently asked questions
More ways to connect
More tools for OpenCode
Use ProxiedMail with other agents
Open your OpenCode agent in one click.
NoClick runs OpenCode for you with ProxiedMail wired in as tools. Connect your account and run.