# An inbox you drive from inside the chat.

Most Gmail MCP servers hand your agent a wall of JSON. DaySurface renders the product - a composer and a ranked inbox - right where your agent already is.

## How it works

1. **Add one URL** - Paste the endpoint into any MCP client that speaks streamable HTTP. No account, no install, no API key.
2. **Sign in to Google** - OAuth in the browser, one minimal Gmail scope. Disconnect drops the stored connection and asks Google to revoke access.
3. **Ask** - Your agent ranks the inbox and drafts replies - banked against each thread's history.
4. **Edit and send** - Every draft opens where you can change it. Nothing leaves until you press send.

## Why it's different

### Interactive UI, not just JSON
DaySurface renders MCP Apps - sandboxed UI that lives inside the chat. Review and edit a draft in a real composer, then triage a ranked inbox in an embedded dashboard, all without leaving your agent. The inbox ranking and triage flow exist because the interactive surface makes them useful; other Gmail MCPs return raw search results and stop there.

### MCP, CLI, API interfaces
Every tool is a pure function in a shared registry, exposed identically over a CLI, an MCP server, and a plain HTTP API. Build once and call it from your shell, any MCP client, or a script - behavior never drifts between interfaces. Most Gmail MCPs are single-transport: stdio-only, or a hosted endpoint you can't run locally.

### Open source and self-hostable
The whole server is open source and ships with a Dockerfile and deploy config, so you can run it on your own infrastructure with your own OAuth credentials and encrypted token storage. Aggregator gateways route your mail through a proprietary service you don't control.

See the full capability matrix against other Gmail MCP servers at https://daysurface.com/compare.

## Get started

Add DaySurface to your MCP client: https://daysurface.com/connect. Why we built it: https://daysurface.com/story.