Gmail MCP Server

Enables AI assistants to interact with Gmail and Calendar services through a Model Context Protocol (MCP) server.

Local serverstdioTypeScript 1

What is the Gmail MCP server?

Gmail MCP server exists for a simple reason — assistants are far more useful when they can act on Gmail directly instead of describing what you should do. Enables AI assistants to interact with Gmail and Calendar services through a Model Context Protocol (MCP) server.

What the assistant can call

Once Gmail is connected, these are the calls the assistant has available:

  • Security — The Security tool exposed by this server
  • Prerequisites — The Prerequisites tool exposed by this server
  • Installation — 1. Clone and install dependencies: bash git clone [repository-url] cd gmail-mcp-server npm install

Configuration and credentials

You will need 3 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js (v14 or higher) - npm (v6 or higher) - Google Cloud Platform account with Gmail and Calendar APIs enabled - OAuth 2.0 credentials with appropriate scopes

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

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 — Security, Prerequisites, Installation — is a fair guide to whether it matches your workflow. It is maintained by zacco16; 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.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the gmail mcp server does with a few real requests.

Available tools

ToolWhat it does
SecurityThe Security tool exposed by this server.
PrerequisitesThe Prerequisites tool exposed by this server.
Installation1. Clone and install dependencies: bash git clone [repository-url] cd gmail-mcp-server npm install

Configuration

  • Node.js (v14 or higher) - npm (v6 or higher) - Google Cloud Platform account with Gmail and Calendar APIs enabled - OAuth 2.0 credentials with appropriate scopes
VariableDescriptionRequired
GOOGLE_CLIENT_IDConfiguration value read at startup.Optional
GOOGLE_CLIENT_SECRETCredential the server authenticates with.Yes
GOOGLE_REFRESH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Gmail to Security.
  • Use Gmail to Prerequisites.
  • Use Gmail to Installation.

Frequently asked questions

You need Node.js (v14+), npm (v6+), a Google Cloud Platform account with Gmail and Calendar APIs enabled, and OAuth 2.0 credentials with appropriate scopes.