# DaySurface vs Google Workspace MCP

> Gmail done deeply vs. Workspace done broadly. Google Workspace MCP covers a huge surface - Gmail, Calendar, Drive and Docs - as headless tools you run yourself. It's a great fit when you need the whole suite. DaySurface goes the other way: deep on Gmail with an interactive in-chat composer and ranked-inbox dashboard, a minimal single Gmail scope, and the same tools exposed over CLI and HTTP as well as MCP.

Google Workspace MCP (Workspace suite): Broad Google Workspace coverage (Gmail, Calendar, Drive, Docs) over MCP.
- Google Workspace MCP: https://github.com/taylorwilsdon/google_workspace_mcp
- DaySurface: https://daysurface.com

Accurate as of June 2026. Comparison reflects publicly documented capabilities as of June 2026. The MCP ecosystem moves fast - if something here is out of date, open an issue and we'll fix it.

## Which to choose

- Choose DaySurface if: Gmail is the priority and you want an interactive inbox UI, scope minimalism, and multi-transport access.
- Choose Google Workspace MCP if: you need Calendar, Drive and Docs alongside Gmail in one server.

## Side by side

| Capability | DaySurface | Google Workspace MCP |
| --- | --- | --- |
| Interactive in-chat UI (MCP Apps) - Composer + ranked-inbox dashboard rendered inside the chat client. | yes | no (JSON only) |
| Built-in inbox triage & ranking - An importance-ranked inbox out of the box, not just raw search. | yes | no (raw search) |
| One codebase → CLI + MCP + HTTP - Identical tools across every interface, no duplicated logic. | yes | partial (MCP only) |
| Zero-install (remote streamable HTTP) - Connect by pasting a URL - nothing to install locally. | yes | no (self-run) |
| Open source & self-hostable - Run the full server on your own infrastructure. | yes | yes |
| Minimal scope + encrypted tokens - A single Gmail scope with tokens encrypted at rest. | yes | partial (broad scopes) |

## What makes DaySurface 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.

## More

- All comparisons: https://daysurface.com/compare.md
- Get connected: https://daysurface.com/connect.md
- Full description for LLMs: https://daysurface.com/llms-full.txt