Native Gmail MCP server: search, labels, archive, trash, attachments, and snooze.
If you already use Mailwarden, the mailwarden mcp server is the piece that lets your assistant work with it directly. Native Gmail MCP server: search, labels, archive, trash, attachments, and snooze.
A reliable, native Gmail MCP server — full mailbox triage for AI assistants, with the feature nobody else ships: snooze.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
search — Gmail query syntax → thread summaries (from/subject/date/labels/snippet); read-state/category predicates are re-verified against each hit's liveget_thread — Full thread: headers, plaintext + HTML bodies, attachment metadatalist_labels — All labels (system + user)create_label — Create a user label (idempotent; nested via Parent/Child) and return its idmodify_labels — Add/remove labels by name or id — an unknown name in add is auto-created (archive = remove INBOX, read = remove UNREAD)download_attachment — Save an attachment to a local path (never overwrites — collisions get a numeric suffix)list_filters — All Gmail filters (criteria + label actions); surfaces any forward address on existing filters for auditingcreate_filter — Create a server-side auto-triage rule (criteria → label actions only; no forwarding — see below). Optionally applyToExisting to also sweepdelete_filter — Delete a filter by idInstallation goes through your MCP client rather than a global install: point it at mailwarden on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: MAILWARDEN_TOKEN, MAILWARDEN_ALLOW_NO_TOKEN, MAILWARDEN_HOST. 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. Mailwarden's toolset — search, get_thread, list_labels and 6 more — is a fair guide to whether it matches your workflow. It is maintained by csitte; 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 |
|---|---|
| search | Gmail query syntax → thread summaries (from/subject/date/labels/snippet); read-state/category predicates are re-verified against each hit's live labels; paginated via pageToken/nextPageToken |
| get_thread | Full thread: headers, plaintext + HTML bodies, attachment metadata |
| list_labels | All labels (system + user) |
| create_label | Create a user label (idempotent; nested via Parent/Child) and return its id |
| modify_labels | Add/remove labels by **name or id** — an unknown name in add is auto-created (archive = remove INBOX, read = remove UNREAD) |
| download_attachment | Save an attachment to a local path (never overwrites — collisions get a numeric suffix) |
| list_filters | All Gmail filters (criteria + label actions); surfaces any forward address on existing filters for auditing |
| create_filter | Create a server-side auto-triage rule (criteria → label actions only; **no forwarding** — see below). Optionally applyToExisting to also sweep matching mail already in the mailbox |
| delete_filter | Delete a filter by id |
{
"mcpServers": {
"mailwarden": {
"command": "npx",
"args": ["-y", "mailwarden"],
"env": {
"MAILWARDEN_TOKEN": "your-value",
"MAILWARDEN_ALLOW_NO_TOKEN": "your-value",
"MAILWARDEN_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MAILWARDEN_TOKEN | Credential the server authenticates with. | Yes |
| MAILWARDEN_ALLOW_NO_TOKEN | Credential the server authenticates with. | Yes |
| MAILWARDEN_HOST | Endpoint or connection string the server talks to. | 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.