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.
Claude
Triage my inbox and draft replies.
I triaged your inbox. Here's the curated view.
Triage my inbox and draft replies.
Here's your inbox, triaged by priority.
Triage my inbox and draft replies.
On it. Running the inbox tool now.
goose · 9:42 AM
Triage my inbox and draft replies.
Triaged your inbox in agent mode:
Ask Copilot
How it works
-
01 Add one URL
Paste the endpoint into any MCP client that speaks streamable HTTP. No account, no install, no API key.
-
02 Sign in to Google
OAuth in the browser, one minimal Gmail scope. Disconnect drops the stored connection and asks Google to revoke access.
-
03 Ask
Your agent ranks the inbox and drafts replies - banked against each thread's history.
-
04 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
A real composer and a ranked inbox, rendered inside the chat.
MCP, CLI, API interfaces
One service registry behind all three. Behaviour never drifts.
Open source and self-hostable
Your infrastructure, your OAuth credentials, no gateway in between.
Full capability matrix vs other Gmail MCP servers on the comparison page.
Ship your MCP server today.
Clone the repo, deploy it, and point your agent at the URL.
https://mcp.daysurface.com/mcp 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.
If the link does not work
- 1 Open Claude → Settings → Connectors
- 2 Click “Add custom connector”
- 3 Paste the URL above, then click Add and complete sign-in
Copies the URL, then opens the empty dialog - just paste. Needs Developer mode on first.
Full click-path, if the link does not work
- 1 Settings → Connectors → Advanced settings → Developer mode on
- 2 Back on Connectors, click Create
- 3 Paste the URL, name it, Authentication → OAuth
- 4 Tick the risk box, click Create
- 5 New chat, so the tools menu refreshes
Run this in your terminal - it adds the server to Claude Code.
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.
Opens Cursor and adds the server. Not working? Copy the URL above and add it under Settings → MCP.
Opens VS Code and adds the server. Requires Copilot agent mode.
Opens Goose and adds the extension over streamable HTTP.
Paste this into Cline - it will add the server for you.
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.
Paste this into Zed - it will add the server for you.
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.
Paste this into Windsurf - it will add the server for you.
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.
Paste this into Any MCP client - it will add the server for you.
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.
- Three transports, one codebase
- Headless or interactive tools
- Streamable HTTP, one port
- Open source, self-hostable