Triage, draft, sign - without leaving chat.

A real email composer and a ranked inbox, right inside Claude, ChatGPT, or your favorite agent. Your agent triages and writes; you edit and send.

https://mcp.daysurface.com/mcp
Add to Claude

Opens Claude with the name and URL already filled in - just click Add. Claude flags it as suggested by an external link; that's expected. On Team and Enterprise plans an admin adds it.

Didn't work? Add it manually
  1. 1 Open Claude → Settings → Connectors
  2. 2 Click “Add custom connector”
  3. 3 Paste the URL above, then click Add and complete sign-in
Claude

Triage my inbox and draft replies.

I triaged your inbox. Here's the curated view.

gmail_curate_inbox ✓
Curated inbox
123
  • D
    Re: Q3 contract - countersignature 0.86
    Draft × Unread awaiting your reply
    Dana Whitfield
    Looks good on our end. Just need your signature on page 4 before EOD.
    2 days ago
  • P
    Design review for v2 dashboard 0.61
    Unread mentions you
    Priya Nair
    Pushing our review an hour, calendar invite updated.
    5 hours ago
  • S
    Your invoice is ready 0.42
    has attachment
    [email protected]
    Your monthly statement is attached. Total due $1,204.00.
    1 day ago
Inbox
Re: Q3 contract - countersignature
D Dana Whitfield <[email protected]>

Looks good on our end. Just need your signature on page 4 before EOD - once that's in we can countersign and get this filed today.

Draft a researched reply to the Q3 contract thread from Dana.

gmail_reply_to_thread ✓

Researched the thread and drafted a reply, saved to your inbox.

Inbox Draft ready
Re: Q3 contract - countersignature
D Dana Whitfield Just need your signature on page 4… 2d
To [email protected]
Draft saved
Reply to Claude…

Works with every MCP client

  • Claude
  • Codex
  • Cursor
  • ChatGPT
  • VS Code
  • OpenClaw
  • Goose

One codebase, every surface

Write a tool once. Ship it to agents, scripts, and services without rewrites.

  1. 01

    Three transports, zero duplication

    Every tool is a pure function in a shared registry, exposed identically over CLI, MCP, and HTTP. Behavior never drifts between interfaces.

  2. 02

    Headless or interactive

    Return data for autonomous agents, or opt into enhanced tools that elicit input, attach media, and render sandboxed UI dashboards.

How DaySurface compares

Most Gmail MCPs hand your agent raw API calls and a wall of JSON. DaySurface is a Gmail product: an interactive inbox you can drive from inside the chat, open source and yours to host.

01

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.

02

One codebase, three transports

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.

03

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.

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

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.

See the full comparison

Trusted by builders

“We had a production MCP server in front of our agents the same afternoon. The shared registry meant our CLI and API just worked too.”
Placeholder NameStaff Engineer, Placeholder Co.
“The typed schemas are the killer feature. Our agent stopped guessing argument shapes overnight.”
Placeholder NameFounder, Placeholder AI

Pricing & licensing

Open source under the MIT license and free to self-host - no setup fee, no seat minimum. Pay only when you want us to run and scale it for you.

Open Source

$0forever

MIT-licensed. Self-host the full server on your own infrastructure - zero setup cost, no license fee.

  • MIT license - fork, modify, and ship freely
  • All three transports: CLI, MCP, HTTP API
  • Interactive MCP Apps (composer + ranked inbox)
  • Your own OAuth credentials & encrypted tokens
  • Community support
Get the source

Hosted Pro

$20/mo

We run the streamable-HTTP server for you. No infrastructure to manage, paste-a-URL setup.

  • Managed cloud deployment (zero ops)
  • Hosted OAuth 2.1 & encrypted token storage
  • Usage analytics & monitoring
  • Priority support
Start free trial

Team

Custom

For teams running agents in production, with commercial licensing options.

  • SSO + audit logs
  • Commercial / OEM licensing
  • Uptime SLA
  • Dedicated support & onboarding
Contact sales

Ask AI about this

Have your assistant explain what it does, how it compares, and how to connect it.

Ask in ChatGPT Ask in Perplexity Ask in Claude

Frequently asked questions

What can it actually do with my email?

Rank your inbox by what needs attention, search and read threads, draft and send replies in a real composer, manage labels, archive, handle attachments, and fill and sign PDF attachments without leaving the chat. 34 tools in total, all through the official Gmail API.

Can it send email without me?

The tools are built so replies land in a composer you review and edit first - your agent writes, you press send. Signing is stronger still: the assistant can fill a PDF's fields, but the signature itself is a step only you can complete by typing your own name. It cannot sign on your behalf.

Do you read or train on my email?

No. Your email is never sent to an AI model by us - DaySurface runs no LLM inference on Gmail content, and the inbox ranking is deterministic code, not a model. Mail goes only to the AI client you chose and connected, under that client's own terms. Access uses Google's gmail.modify scope; see the privacy policy for the full detail.

Do I need to install anything to use it?

No. The server runs over streamable HTTP, so connecting is just adding its URL to your client - one click in Claude, Cursor, VS Code, and Goose. No local install, runtime, or download. (Self-hosting is a separate, optional step.)

Which clients does it work with?

Anything that speaks the Model Context Protocol: Claude, ChatGPT, Claude Code, Cursor, VS Code, Goose, Cline, Zed, Windsurf, and more. Pick yours in the connect box above - some get a one-click install link, the rest take a pasted URL or a setup prompt.

Does it work on mobile?

Yes, anywhere your agent runs. It's a remote server with nothing to install locally, so it works in any agent app with a mobile client, including the Claude and ChatGPT mobile apps.

Can I self-host?

Yes. The whole thing is open source and ships with a Dockerfile and Railway config, so you can run it on your own infrastructure with your own Google OAuth credentials. Deploy it anywhere that runs a container.

Is this just another Gmail API wrapper?

No. Most Gmail MCPs (like GongRzhe's) wrap the Gmail API and return JSON. DaySurface renders interactive MCP Apps - a composer you edit drafts in and a ranked inbox you triage - directly inside the chat, and exposes the same tools over CLI and HTTP, not just MCP. See the comparison at /compare.

How is it different from Composio, Zapier, or Google Workspace MCP?

Those are broad gateways or suites where Gmail is one generic toolkit among many. DaySurface goes deep on Gmail with an interactive in-chat inbox, and it's open source and self-hostable so your mail never routes through a proprietary service. Full breakdown at /compare.

Put your inbox in your chat.

Pick your client, add the server, and your agent can start triaging today.

https://mcp.daysurface.com/mcp
Add to Claude

Opens Claude with the name and URL already filled in - just click Add. Claude flags it as suggested by an external link; that's expected. On Team and Enterprise plans an admin adds it.

Didn't work? Add it manually
  1. 1 Open Claude → Settings → Connectors
  2. 2 Click “Add custom connector”
  3. 3 Paste the URL above, then click Add and complete sign-in
  • Ranked inbox triage
  • Drafts you edit, not approve
  • Fill and sign PDFs in-thread
  • Open source, self-hostable 
# DaySurface - An MCP server for Gmail

> An MCP server for Gmail: triage a ranked inbox, draft replies in a real composer, and fill and sign PDF attachments - inside Claude, ChatGPT, or any MCP client.

Triage, draft, sign - without leaving chat. A real email composer and a ranked inbox, right inside Claude, ChatGPT, or your favorite agent. Your agent triages and writes; you edit and send.

- Website: https://daysurface.com
- MCP endpoint (streamable HTTP): https://mcp.daysurface.com/mcp
- MCP server name: daysurface
- Documentation: https://docs.daysurface.com
- Source code: https://github.com/Miyamura80/DaySurface

## What it is

DaySurface is a Model Context Protocol (MCP) server. It exposes a single
shared service registry over three interfaces - a CLI, an MCP server
(streamable HTTP), and a plain HTTP API - so the same typed tools behave
identically no matter how they are called. Any agent that speaks MCP can
discover and call its tools.

## When to use

Reach for DaySurface when a task needs Gmail actions - reading, searching, triaging, drafting, or sending mail - on the user's behalf.

Use DaySurface when:
- The user asks to read, search, or summarize their email (e.g. "what did Sarah send about the contract?").
- The user asks to triage or prioritize their inbox - call `gmail_curate_inbox` to rank threads by importance.
- The user asks to draft, reply to, or send a message - draft first and let the user review before sending.
- Another task needs a fact that lives in the user's mail (an invoice total, a confirmation number, a meeting time).

Do not use DaySurface when:
- The request is about a different mail provider (Outlook, Proton) - these tools are Gmail-only.
- The user has not connected an account or granted access - complete the auth flow (see auth.md) first.
- The task is purely local or computational and needs no access to the user's mailbox.

## Connecting

Add the streamable-HTTP endpoint https://mcp.daysurface.com/mcp to any MCP client. Nothing to
install locally. Server name: `daysurface`.

### Claude
One-click install link on the site.
Opens Claude with the name and URL already filled in - just click Add. Claude flags it as suggested by an external link; that's expected. On Team and Enterprise plans an admin adds it.

### ChatGPT
1. Settings → Connectors (newer builds: Apps & Connectors)
2. Advanced settings → turn on Developer mode
3. Back on Connectors, click Create
4. Paste the URL above, name it, then click Create
5. Start a new chat so the tools menu refreshes

### Claude Code
Run this in a terminal:

claude mcp add --transport http --scope user daysurface https://mcp.daysurface.com/mcp
Run it in your terminal, then /mcp in a session to sign in.

### Cursor
One-click install link on the site.
Opens Cursor and adds the server. Not working? Copy the URL above and add it under Settings → MCP.

### VS Code
One-click install link on the site.
Opens VS Code and adds the server. Requires Copilot agent mode.

### Goose
One-click install link on the site.
Opens Goose and adds the extension over streamable HTTP.

### Cline
Paste this into the agent:

Add a remote MCP server, then verify it connects.

  Name:      daysurface
  Endpoint:  https://mcp.daysurface.com/mcp
  Transport: streamable HTTP (remote, not stdio)
  Auth:      OAuth in the browser, no key to paste

Use THIS client's own config keys - they differ:
VS Code "servers", Cursor/Cline "mcpServers",
Zed "context_servers", Windsurf "serverUrl" not "url".
Keep existing servers. Show me the diff, then say
what to click to finish sign-in.
Or add it by hand: MCP Servers → Remote Servers → Streamable HTTP.

### Zed
Paste this into the agent:

Add a remote MCP server, then verify it connects.

  Name:      daysurface
  Endpoint:  https://mcp.daysurface.com/mcp
  Transport: streamable HTTP (remote, not stdio)
  Auth:      OAuth in the browser, no key to paste

Use THIS client's own config keys - they differ:
VS Code "servers", Cursor/Cline "mcpServers",
Zed "context_servers", Windsurf "serverUrl" not "url".
Keep existing servers. Show me the diff, then say
what to click to finish sign-in.
Or add it by hand: Settings → AI → MCP Servers → Add Remote Server.

### Windsurf
Paste this into the agent:

Add a remote MCP server, then verify it connects.

  Name:      daysurface
  Endpoint:  https://mcp.daysurface.com/mcp
  Transport: streamable HTTP (remote, not stdio)
  Auth:      OAuth in the browser, no key to paste

Use THIS client's own config keys - they differ:
VS Code "servers", Cursor/Cline "mcpServers",
Zed "context_servers", Windsurf "serverUrl" not "url".
Keep existing servers. Show me the diff, then say
what to click to finish sign-in.
Windsurf uses “serverUrl”, not “url” - a snippet copied from another client will fail silently.

### Any MCP client
Paste this into the agent:

Add a remote MCP server, then verify it connects.

  Name:      daysurface
  Endpoint:  https://mcp.daysurface.com/mcp
  Transport: streamable HTTP (remote, not stdio)
  Auth:      OAuth in the browser, no key to paste

Use THIS client's own config keys - they differ:
VS Code "servers", Cursor/Cline "mcpServers",
Zed "context_servers", Windsurf "serverUrl" not "url".
Keep existing servers. Show me the diff, then say
what to click to finish sign-in.
Anything that speaks MCP over streamable HTTP works - there is nothing to install.

## Features

### Three transports, zero duplication
Every tool is a pure function in a shared registry, exposed identically over CLI, MCP, and HTTP. Behavior never drifts between interfaces.

### Headless or interactive
Return data for autonomous agents, or opt into enhanced tools that elicit input, attach media, and render sandboxed UI dashboards.

## How it compares

Most Gmail MCPs hand your agent raw API calls and a wall of JSON. DaySurface is a Gmail product: an interactive inbox you can drive from inside the chat, open source and yours to host.

What makes DaySurface different (as of June 2026):
- **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.
- **One codebase, three transports**: 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.

### DaySurface vs GongRzhe Gmail-MCP-Server
The open-source Gmail MCP, upgraded. GongRzhe's server is a faithful, well-loved wrapper around the Gmail API - around a dozen tools for send, draft, read, search, labels and attachments, run locally over stdio with a credentials file on disk. You get clean primitives and JSON back. DaySurface shares the open-source spirit but goes further: it renders an interactive composer and a ranked-inbox dashboard inside the chat, and the same tools are reachable over a CLI and an HTTP API, not just stdio.

- Choose DaySurface if: you want an in-chat composer and inbox triage UI, remote zero-install access, and the same tools available over CLI and HTTP as well as MCP.
- Choose GongRzhe Gmail-MCP-Server if: you want a minimal, local, stdio-only Gmail wrapper to embed in a desktop client and you're happy driving everything through JSON tool calls.
- Full comparison: https://daysurface.com/vs/gongrzhe-gmail-mcp

### DaySurface vs Composio Gmail
A Gmail product, not a Gmail endpoint in a 500-app gateway. Composio's strength is breadth: one managed endpoint and hosted OAuth across hundreds of SaaS apps, with Gmail exposed as a generic search / read / draft / send toolkit. DaySurface trades breadth for depth on email - an interactive composer and ranked-inbox dashboard rendered in the chat - and it's open source, so you self-host with your own credentials instead of routing mail through a proprietary gateway.

- Choose DaySurface if: email is the job: you want an interactive in-chat inbox, full control of your own deployment, and the ability to run the same tools over CLI and HTTP.
- Choose Composio Gmail if: you need one managed endpoint spanning many SaaS apps and you don't want to run any infrastructure yourself.
- Full comparison: https://daysurface.com/vs/composio-gmail

### DaySurface vs Zapier & Pipedream MCP
Built for an agent in the loop, not a no-code workflow. Zapier and Pipedream expose Gmail as actions inside their automation platforms - great for fire-and-forget workflows, with tools often auto-generated from API specs. DaySurface is purpose-built for a human-in-the-loop agent: an interactive composer where you review and edit before anything sends, a ranked inbox you triage in-chat, and an open-source codebase you host yourself rather than orchestrate through a workflow runner.

- Choose DaySurface if: you want an agent that drafts and triages with you interactively, a focused Gmail surface, and a server you own and self-host.
- Choose Zapier & Pipedream MCP if: your goal is automated, multi-app workflows triggered by events, and you're already invested in their builder.
- Full comparison: https://daysurface.com/vs/zapier-pipedream-mcp

### 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.

- 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.
- Full comparison: https://daysurface.com/vs/google-workspace-mcp

See the full comparison and capability matrix at https://daysurface.com/compare.

## Compatible clients

Works with every MCP client, including: Claude, Codex, Cursor, ChatGPT, VS Code, OpenClaw, Goose.

## How to connect

1. Copy the MCP server URL: https://mcp.daysurface.com/mcp
2. Add it to your client (server name `daysurface`):
   - Claude: one-click install (deep link supported).
   - ChatGPT: Settings → Connectors (newer builds: Apps & Connectors) → Advanced settings → turn on Developer mode → Back on Connectors, click Create → Paste the URL above, name it, then click Create → Start a new chat so the tools menu refreshes
   - Claude Code: run `claude mcp add --transport http --scope user daysurface https://mcp.daysurface.com/mcp`
   - Cursor: one-click install (deep link supported).
   - VS Code: one-click install (deep link supported).
   - Goose: one-click install (deep link supported).
   - Cline: paste the setup prompt shown under "Connecting" above.
   - Zed: paste the setup prompt shown under "Connecting" above.
   - Windsurf: paste the setup prompt shown under "Connecting" above.
   - Any MCP client: paste the setup prompt shown under "Connecting" above.
3. Your agent discovers the tools automatically and calls them with typed inputs.

## FAQ

### What can it actually do with my email?
Rank your inbox by what needs attention, search and read threads, draft and send replies in a real composer, manage labels, archive, handle attachments, and fill and sign PDF attachments without leaving the chat. 34 tools in total, all through the official Gmail API.

### Can it send email without me?
The tools are built so replies land in a composer you review and edit first - your agent writes, you press send. Signing is stronger still: the assistant can fill a PDF's fields, but the signature itself is a step only you can complete by typing your own name. It cannot sign on your behalf.

### Do you read or train on my email?
No. Your email is never sent to an AI model by us - DaySurface runs no LLM inference on Gmail content, and the inbox ranking is deterministic code, not a model. Mail goes only to the AI client you chose and connected, under that client's own terms. Access uses Google's gmail.modify scope; see the privacy policy for the full detail.

### Do I need to install anything to use it?
No. The server runs over streamable HTTP, so connecting is just adding its URL to your client - one click in Claude, Cursor, VS Code, and Goose. No local install, runtime, or download. (Self-hosting is a separate, optional step.)

### Which clients does it work with?
Anything that speaks the Model Context Protocol: Claude, ChatGPT, Claude Code, Cursor, VS Code, Goose, Cline, Zed, Windsurf, and more. Pick yours in the connect box above - some get a one-click install link, the rest take a pasted URL or a setup prompt.

### Does it work on mobile?
Yes, anywhere your agent runs. It's a remote server with nothing to install locally, so it works in any agent app with a mobile client, including the Claude and ChatGPT mobile apps.

### Can I self-host?
Yes. The whole thing is open source and ships with a Dockerfile and Railway config, so you can run it on your own infrastructure with your own Google OAuth credentials. Deploy it anywhere that runs a container.

### Is this just another Gmail API wrapper?
No. Most Gmail MCPs (like GongRzhe's) wrap the Gmail API and return JSON. DaySurface renders interactive MCP Apps - a composer you edit drafts in and a ranked inbox you triage - directly inside the chat, and exposes the same tools over CLI and HTTP, not just MCP. See the comparison at /compare.

### How is it different from Composio, Zapier, or Google Workspace MCP?
Those are broad gateways or suites where Gmail is one generic toolkit among many. DaySurface goes deep on Gmail with an interactive in-chat inbox, and it's open source and self-hostable so your mail never routes through a proprietary service. Full breakdown at /compare.

## Machine-readable resources

- llms.txt: https://daysurface.com/llms.txt
- llms-full.txt: https://daysurface.com/llms-full.txt
- agents.md: https://daysurface.com/agents.md
- auth.md (agent auth manifest): https://daysurface.com/auth.md
- pricing.md (machine-readable pricing): https://daysurface.com/pricing.md
- Agent skills (JSON): https://daysurface.com/.well-known/agent-skills/index.json
- Agent skills (shell pointer): https://daysurface.com/skills.sh
- MCP discovery (JSON): https://daysurface.com/.well-known/mcp.json
- Sitemap: https://daysurface.com/sitemap.xml
- Schema map: https://daysurface.com/schemamap.xml