MCP Implementation for Gmail Services
Connect Gmail to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Implementation for Gmail Services. The gmail mcp server is what makes that connection.
To run this MCP server, you will need to set up a Google API Client for your organization, with each user running a script to retrieve their own OAuth refresh token.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Dependencies — The Dependencies tool exposed by this serverDelegates — The Delegates tool exposed by this serverFilters — The Filters tool exposed by this serverBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: CLIENT_ID, CLIENT_SECRET, REFRESH_TOKEN, GMAIL_OAUTH_PATH, GMAIL_CREDENTIALS_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Gmail's toolset — Dependencies, Delegates, Filters — is a fair guide to whether it matches your workflow. It is maintained by shinzo-labs; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Dependencies | The Dependencies tool exposed by this server. |
| Delegates | The Delegates tool exposed by this server. |
| Filters | The Filters tool exposed by this server. |
{
"mcpServers": {
"gmail-mcp-shinzo-labs": {
"command": "npx",
"args": ["-y", "@shinzolabs/gmail-mcp"],
"env": {
"CLIENT_ID": "your-value",
"CLIENT_SECRET": "your-value",
"REFRESH_TOKEN": "your-value",
"GMAIL_OAUTH_PATH": "your-value",
"GMAIL_CREDENTIALS_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CLIENT_ID | Configuration value read at startup. | Optional |
| CLIENT_SECRET | Credential the server authenticates with. | Yes |
| REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| GMAIL_OAUTH_PATH | Filesystem location the server is allowed to use. | Optional |
| GMAIL_CREDENTIALS_PATH | Filesystem location the server is allowed to use. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.