@mcp-z/mcp-gmail
MCP server for Gmail integration with OAuth authentication, message search, batch operations, and Google Sheets export
Requires Node.js >=20. The examples use npx, included with npm, to run this server and @mcp-z/cli.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @mcp-z/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add mcp-z-mcp-gmail -- npx -y @mcp-z/mcp-gmail@2.5.1Execute em um terminal.
{ "mcpServers": { "mcp-z-mcp-gmail": { "command": "npx", "args": [ "-y", "@mcp-z/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
MCP server for Gmail integration with OAuth authentication, message search, batch operations, and Google Sheets export
Requires Node.js >=20. The examples use npx, included with npm, to run this server and @mcp-z/cli.
MCP server for Gmail integration with OAuth authentication, message search, batch operations, and Google Sheets export
MCP supports stdio and HTTP.
Both the 2025 and 2026-07-28 protocol revisions are served, over either transport, from the same
server. Your client negotiates whichever it speaks. A 2025 client keeps working with no change,
and support for it is not being dropped. The 2026-07-28 revision is stateless, so a client speaking
it sends no initialize handshake and carries no session id.
Stdio
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["-y", "@mcp-z/mcp-gmail"]
}
}
}
HTTP
{
"mcpServers": {
"gmail": {
"type": "http",
"url": "http://localhost:9002/mcp",
"start": {
"command": "npx",
"args": ["-y", "@mcp-z/mcp-gmail", "--port=9002"]
}
}
}
}
start is an extension used by npx @mcp-z/cli up to launch HTTP servers for you.
Configure via environment variables or the env block in .mcp.json. The configuration reference below lists every option.
Environment variables:
GOOGLE_CLIENT_ID=your-client-id
GOOGLE_CLIENT_SECRET=your-client-secret
Example (stdio) - Create .mcp.json:
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["-y", "@mcp-z/mcp-gmail"],
"env": {
"GOOGLE_CLIENT_ID": "your-client-id"
}
}
}
}
Example (http) - Create .mcp.json:
{
"mcpServers": {
"gmail": {
"type": "http",
"url": "http://localhost:3000/mcp",
"start": {
"command": "npx",
"args": ["-y", "@mcp-z/mcp-gmail", "--port=3000"],
"env": {
"GOOGLE_CLIENT_ID": "your-client-id"
}
}
}
}
}
Local (default): omit REDIRECT_URI → ephemeral loopback. Cloud: set REDIRECT_URI to your public /oauth/callback and expose the service publicly.
Note: the start block is a helper in npx @mcp-z/cli up for starting an HTTP server from your .mcp.json. See @mcp-z/cli for details.
Environment variables:
AUTH_MODE=service-account
GOOGLE_SERVICE_ACCOUNT_KEY_FILE=/path/to/service-account.json
Example:
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["-y", "@mcp-z/mcp-gmail", "--auth=service-account"],
"env": {
"GOOGLE_SERVICE_ACCOUNT_KEY_FILE": "/path/to/service-account.json"
}
}
}
}
HTTP only. Requires a public base URL. CSV export and /files are disabled in DCR mode; resourceStoreUri is ignored.
{
"mcpServers": {
"gmail-dcr": {
"command": "npx",
"args": [
"-y",
"@mcp-z/mcp-gmail",
"--auth=dcr",
"--port=3456",
"--base-url=https://oauth.example.com"
],
"env": {
"GOOGLE_CLIENT_ID": "your-client-id",
"GOOGLE_CLIENT_SECRET": "your-client-secret"
}
}
}
}
# Start the configured server and list its tools
npx -y @mcp-z/cli inspect --servers gmail --tools
# Call a tool after authorizing Gmail
npx -y @mcp-z/cli call-tool gmail message-search '{"query":"from:[email protected]"}'
See server.json for all supported environment variables, CLI arguments, and defaults.
OAuth tokens (TOKEN_STORE_URI) and DCR registrations (DCR_STORE_URI) are stored through keyv-registry, which picks an adapter from the URI protocol.
file:// (the default, under ~/.mcp-z/) and memory:// work with no extra setup.
Any other backend needs its adapter installed alongside this server. Adapters are resolved with require(), so a globally installed server finds a globally installed adapter:
npm install -g @mcp-z/mcp-gmail @keyv/redis
TOKEN_STORE_URI=redis://localhost:6379 mcp-gmail
A protocol whose adapter is missing fails at startup naming the package to install.
MCP server for Gmail integration with OAuth authentication, message search, batch operations, and Google Sheets export
{ "mcpServers": { "mcp-z-mcp-gmail": { "command": "npx", "args": [ "-y", "@mcp-z/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@mcp Z/mcp Gmail roda localmente via stdio.
Última verificação: 2026-11-19. MCP server for Gmail integration with OAuth authentication, message search, batch operations, and Google Sheets export