Connect Gmail to Microsoft 365 Copilot
An admin adds this one - there is no per-user settings screen.
Microsoft 365 Copilot reaches third-party MCP servers through connectors managed at the tenant level, so this is not something an individual turns on for themselves. There are two documented routes: a custom connector in the Microsoft 365 admin center, which makes the server available across the tenant, or an MCP tool on a specific Copilot Studio agent. Both need elevated rights.
The server URL
https://mcp.daysurface.com/mcp
Transport is streamable HTTP. Auth is OAuth in the browser - there is no key to paste and no account to create.
Before you start
- A Google account with Gmail.
- Global Administrator or AI Administrator in the Microsoft 365 admin center for the connector route.
- For the admin-center route, authentication configured in advance - the connector form asks for a registration ID, not a URL and a password.
Add DaySurface to Microsoft 365 Copilot
-
01 Open the Copilot connectors gallery
Sign in to the Microsoft 365 admin center and go to Copilot, then Connectors. Open the Gallery tab.
-
02 Start a custom connector
Under Created by your org, find the Create a new connector tile and select Add.
-
03 Point it at the MCP server
On the custom connector page, under Connect to MCP server, select Add and supply the DaySurface endpoint along with the registration ID matching your authentication method - the SSO or OAuth registration ID from the Teams Developer Portal.
-
04 Save and roll out
Save to create the connector. It then follows your tenant's normal rollout and consent path rather than appearing instantly for everyone.
-
05 Or add it to one Copilot Studio agent instead
If you want it scoped to a single agent rather than the tenant, open that agent's Tools page in Copilot Studio, choose Add a tool, then New tool, then MCP, and run the onboarding wizard with the endpoint and OAuth 2.0.
What Microsoft 365 Copilot can do once it is connected
Triage a ranked inbox without leaving the chat
The inbox arrives as an interactive dashboard rendered inside the conversation, not as a wall of JSON for the model to summarise. You read, rank and clear threads in place.
Draft replies in a real composer
Replies open in an editable composer you can correct before anything sends. Nothing leaves your account on the model's say-so alone.
Fill and sign PDF attachments
Attached forms can be filled in from the thread. Signing is a step you complete yourself - the tool never types a signature on your behalf.
Search across threads by meaning, not just keywords
Search runs server-side over your mail and returns threads, so the agent works from what is actually in your inbox rather than what it can hold in context.
This one needs your admin
Microsoft 365 Copilot is provisioned centrally, so there is no button here that finishes the job. Send the steps above to whoever administers your tenant - or, if you want DaySurface on your own account today, add it to a client you control instead.
See the clients you can add yourselfQuestions
Can I add this myself without an admin?
No. Both documented routes need elevated rights - Global or AI Administrator for a tenant connector, and maker access to the agent for the Copilot Studio route. If you want DaySurface on your own account today, use a client you control, such as Claude or ChatGPT.
Microsoft's guidance mentions read-only tools. Does that rule this out?
That guidance is about federated connectors used for grounding, where the tools are search and fetch. DaySurface exposes tools that change mailbox state as well, so check the route you pick against your own tenant policy before rolling it out - and note that sending is gated behind a draft you approve rather than happening on the model's judgement.
Do I need a DaySurface account?
No. There is no account to create and no password to set. You add the server to your client, then sign in to Google when it asks. Authorisation is the whole signup.
Is there an API key to paste?
No. Auth is OAuth in the browser. If a setup guide anywhere tells you to paste a key, it is not describing this server.
What does it get access to?
The Google scopes you approve in the consent screen, and nothing else. You can review them at the moment of sign-in and revoke them later from your Google account.
Can I run it myself instead?
Yes. It is MIT-licensed and self-hostable, and the same tools are exposed over a CLI and a plain HTTP API as well as MCP. Point your client at your own deployment instead of the hosted endpoint.