Gmail Model Context Protocol server with recipient allowlist and local audit log.
Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Gmail Model Context Protocol server with recipient allowlist and local audit log. The mcp mcp server is what makes that connection.
A comprehensive Gmail Model Context Protocol server: 35 tools covering send/preview/confirm, reply, forward, drafts, search, read, attachments, trash, labels, filters, signature, and vacation responder.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Group — ToolsDrafts — create_draft, list_drafts, send_draft, update_draft, delete_draftAttachments — get_message_attachments, download_attachmentTrash — trash_message, untrash_message, trash_thread, untrash_threadLabels — list_labels, create_label, update_label, delete_label, label_message, unlabel_message, label_thread, unlabel_threadFilters — list_filters, create_filter, delete_filterSignature — get_signature, update_signaturemacOS — The macOS tool exposed by this serverThe server ships on PyPI as mcp-gmail-manager, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: GMAIL_MCP_TOKEN. 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.
localhost:8765 to your auth host (typically ssh -L 8765:localhost:8765 user@host)Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Group, Drafts, Attachments and 5 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Group | Tools |
| Drafts | create_draft, list_drafts, send_draft, update_draft, delete_draft |
| Attachments | get_message_attachments, download_attachment |
| Trash | trash_message, untrash_message, trash_thread, untrash_thread |
| Labels | list_labels, create_label, update_label, delete_label, label_message, unlabel_message, label_thread, unlabel_thread |
| Filters | list_filters, create_filter, delete_filter |
| Signature | get_signature, update_signature |
| macOS | The macOS tool exposed by this server. |
{
"mcpServers": {
"gmail-manager": {
"command": "uvx",
"args": ["mcp-gmail-manager"],
"env": {
"GMAIL_MCP_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
localhost:8765 to your auth host (typically ssh -L 8765:localhost:8765 user@host)| Variable | Description | Required |
|---|---|---|
| GMAIL_MCP_TOKEN | Credential the server authenticates with. | Yes |
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.