Skip to content

Gmail MCP servers

23 MCP servers connect an AI client to Gmail, Google's email service, out of 60,252 MCP servers listed. Popular ones include Gmail, Google Gmail and Gmail Tidy MCP. 14 run locally and 11 run remotely. Each page shows how to install it in Claude, Cursor and VS Code.
  1. MCP server that lets AI clients read, search, send and label Gmail via OAuth

    Not checked yet
    • 5 tools
    • Remote
    • Freemium
    • Communication
  2. MCP server that lets AI clients list, read and send Gmail messages

    Not checked yet
    • Remote
    • Open source
    • Communication
  3. Tidy several Gmail accounts from an assistant, with no way to send or delete mail

    Runs locally
    • 23 tools
    • Open source
    • Communication
  4. Self-hosted Gmail MCP server on your own Cloudflare Worker, for multiple Google accounts

    Not checked yet
    • 24 tools
    • Open source
    • Communication
  5. Gmail MCP server: list, read, search and send email, manage drafts and labels.

    Runs locally
    • Communication
  6. Gmail integration with OAuth authentication, message search, batch operations, and…

    Not checked yet
    • Remote
    • Communication
  7. Gmail for AI agents: search, read, download attachments, send, reply, drafts, labels.

    Runs locally
    • Open source
    • Communication
  8. Hosted Gmail MCP server: read, search, and manage messages. Google OAuth2 handled by…

    Not checked yet
    • Remote
  9. MCP server for Gmail with OAuth2 (personal) and service account (Workspace) support.

    Runs locally
    • Open source
    • Communication
  10. Gmail Postmaster Tools v2 — domains, traffic metrics, and compliance via your own Google…

    Runs locally
    • Open source
    • Communication
  11. Allow AI systems to read, send, archive, and manage emails via Gmail.

    Not checked yet
    • Remote
    • Open source
    • Communication
  12. Multi-account Gmail MCP server — read, search, draft, and label across every inbox.

    Runs locally
    • Open source
    • Communication
  13. Minimal MCP server for downloading Gmail attachments to disk. Read-only OAuth by default.

    Runs locally
    • Open source
    • Communication
  14. Manage multiple Gmail accounts in Claude Desktop — search, send, reply, draft, and…

    Runs locally
    • Open source
    • Communication
  15. Send, read, organize emails, manage labels, drafts, and filters

    Runs locally
    • Open source
    • Communication
  16. Manage Gmail end-to-end: search, read, send, draft, label, and organize threads…

    Not checked yet
    • Remote
    • Communication
  17. Manage Gmail messages, threads, labels, drafts, and settings from your workflows. Send…

    Not checked yet
    • Remote
    • Communication
  18. A MCP server for Gmail that lets you search, read, and draft emails and replies.

    Not checked yet
    • Remote
    • Communication
  19. Gmail MCP server — send, read, and search email. By Strider Labs.

    Runs locally
    • Open source
    • Communication
  20. Read emails, send messages, and manage labels in your Gmail account.

    Not checked yet
    • Remote
    • Communication

Questions about Gmail MCP servers

How many Gmail MCP servers are there?

AI-Powered lists 23 MCP servers for Gmail, out of 60,252 MCP servers in the directory. The count changes as servers are added and updated.

What are the most popular Gmail MCP servers?

Gmail, Google Gmail and Gmail Tidy MCP are among the most popular right now. The ranking combines upvotes, recent activity and, for open-source projects, GitHub stars.

How do I connect Claude to Gmail with an MCP server?

Pick a server from the list and open its page. Claude Code adds it with one "claude mcp add" command; Claude Desktop, Cursor and VS Code use a JSON entry in their MCP config file. Most Gmail servers need credentials for Gmail (an API key, token or connection string), set as environment variables or when you sign in.

Should I use a local or a remote Gmail MCP server?

14 of these servers run locally on your machine over stdio and 11 run remotely and are reached by URL. A local server needs Node.js, Python or Docker and keeps your credentials on your machine; a remote server needs nothing installed but is run by its provider, and some ask you to sign in.