Gmail MCP
gongrzheSearches Gmail and reads threads, with optional draft creation
Searches Gmail and reads threads, with optional draft creation On the other side: bridges microsoft graph: mail, calendar, files, and the directory
Whichever tenant you already pay for. There is no meaningful winner here.
Same job, different tenant. Gmail's server is a community project with a token you generate yourself; Microsoft 365's needs an Azure app registration and admin consent. The second is more work to set up and more likely to be blocked by policy — which is also a signal about how sensitive the mailbox is.
| Option | Install | Source | Link |
|---|---|---|---|
| Gmail MCP | npx -y @gongrzhe/server-gmail-autoauth-mcp | Community | Repository ↗ |
| Microsoft 365 MCP | npx -y @softeria/ms-365-mcp-server | Community | Repository ↗ |
You are on Google Workspace and control your own OAuth app.
You are on Microsoft 365 and can get an app registered by whoever owns the tenant.
A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.
Gives an agent scoped read, write, and search access to directories you explicitly allow
Read-only access to a repository's history: status, diffs, commit logs, and blame
Serves version-specific documentation for thousands of libraries, so an agent stops writing code against an API that changed two releases ago
Runs read-only SQL against a Postgres database and returns the schema alongside results, which is what makes it usable without pasting table definitions into the prompt
Searches messages, threads, and channel metadata in a Slack workspace, and can post when given a token with write scope
A code editor built around an agent that can read your whole repo.