A private email workspace and OAuth-protected MCP server for ChatGPT. Connect compatible inboxes and control each AI action. Self-hosted, MIT licensed.
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: 邮件. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository ozandikici/GPTmail;first catalogued 2026-10-10;last seen 2026-10-10。There is no official certification or quality rating here — we record sources and dates only.
GPTmail
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**Every inbox. One private workspace.**
An open-source workspace for your compatible mail accounts, with a password-protected dashboard and an OAuth-protected MCP connection for ChatGPT. Deploy your own instance, connect your inboxes, and decide what your AI assistant can do.
GPTmail brings multiple accounts into one browser workspace. Search and read a selected mailbox, then selectively enable sending, replying, forwarding, flagging, moving and trashing messages. **Each MCP capability is controlled from the dashboard.** Outgoing mail and Trash actions can require a second approval in the dashboard; both approval switches are **ON** by default.
- **Free-tier-friendly:** FastAPI on Vercel + a persistent Upstash Redis database (check each service's current terms and quotas).
- **Multiple providers:** Standard IMAP/SMTP accounts, plus Gmail and Microsoft OAuth after you configure your own provider app registrations.
- **Encrypted credentials:** IMAP/SMTP account records and pending outbound drafts encrypted with Fernet before storage.
- **Remote MCP:** Streamable HTTP at /mcp, compatible with MCP 2025 and the 2026-07-28 stateless revision.
- **OAuth:** Authorization Code + PKCE (S256), Dynamic Client Registration, scoped owner consent, bearer tokens and rotating refresh tokens.
- **Single-owner:** A password-protected private admin dashboard. Your public **source code** does not make your deployed mailbox public.
- **MIT licensed.** Python, HTML, CSS and vanilla JavaScript; no OpenAI API key required.
> **Private by design, with a clear data boundary:** Mail credentials and provider tokens stay in encrypted server-side storage. **Email content you ask ChatGPT to read is sent to ChatGPT.** Email content is untrusted third-party data, not instructions. Sending is initially disabled. GPTmail is an early single-owner project; it has not undergone an independent security audit.
Türkçe kurulum · Mail provider setup · Security · Contributing
Brand assets: transparent logo · launch card · promotion notes.
**Find GPTmail useful? Star the repository** to help others discover it. Setup feedback, bug reports and contributions are welcome. Please keep mailbox content, account details and secrets out of public issues.
Which inboxes can I connect?
| Account type | Connection | Requirements |
|---|---|---|
| Gmail / Google Workspace | Google OAuth + IMAP/SMTP | Your own Google OAuth web app, consent configuration and an account whose policies permit access |
| Outlook.com / Microsoft 365 | Microsoft OAuth + IMAP/SMTP | Your own Entra web app; mailbox/tenant IMAP and SMTP policies still apply |
| iCloud, Yahoo, Zoho, custom domains and other IMAP services | TLS IMAP + optional TLS SMTP | Provider-supported credentials or app password, correct server settings, and a plan that permits IMAP |
| Services without accessible IMAP/SMTP | No direct connection | A separate compatible integration would be needed |
You can add several accounts, including several accounts from the same provider. An account must pass an IMAP connection check before it is saved. SMTP is optional; a readable mailbox does not automatically have permission to send.
**Provider OAuth setup is required.** Google/Microsoft buttons become available only after the deployment has its own client ID and secret. The public repository does not include a shared OAuth app, credentials or connected mail accounts. “Every inbox” expresses the workspace goal; compatibility depends on the provider and account policy. See the setup guide and limitations.
Available MCP tools
| Capability in dashboard | Tools | Initial state |
|---|---|---|
| Read | list_accounts, list_folders, list_messages, search_messages, read_message | **On** |
| Attachments | get_attachment (max 2 MB) | Off |
| Send | send_email | Off |
| Reply | reply_email | Off |