The itch
I have too much email, and I have agents that are finally good enough to help with it. The obvious move was to just let them - read what came in, tell me what actually needs me, draft the replies I keep putting off.
Every option that could do that came bolted to one assistant. Set it up inside that assistant, learn its way of doing things, and your inbox now lives there. That felt backwards. My mail is mine; the agent is a tool I should be free to swap.
Portable on purpose
So the first rule was no lock-in. DaySurface is a Model Context Protocol server, which means any agent that speaks MCP can drive it - Claude today, something else next month, two of them at once if you like. Move setups and your email tooling comes with you. Nothing to re-learn, nothing stranded.
The same tools also run over a plain CLI and an HTTP API, not just MCP. One codebase behind all three, so a script, your shell, and your agent all reach the exact same inbox with the exact same behaviour.
Yours to run
Portability only counts if the thing underneath is yours. So the whole server is open source and ships to self-host with your own Google credentials - your mail never routes through a service you can't inspect or replace.
That's the whole bet: let your agents actually work your inbox, and never let any single one of them own it. It's early and the roadmap is public. If you've wanted the same thing, come try it.
Eito, DaySurface