Gmail

Created By
shinzo-labsa year ago
Overview

what is Gmail MCP?

Gmail MCP is an implementation of the Model Context Protocol (MCP) for the Gmail API, providing a standardized interface for managing emails, including sending, retrieving, and organizing messages.

how to use Gmail MCP?

To use Gmail MCP, set up authentication with the Gmail API by creating a project in the Google Cloud Console, enabling the Gmail API, and configuring OAuth 2.0 credentials. You can then run the MCP using NPX or by manually downloading the repository.

key features of Gmail MCP?

  • Complete coverage of the Gmail API including messages, threads, labels, drafts, and settings.
  • Support for sending, drafting, and managing emails.
  • Label management with customizable settings.
  • Thread operations for managing conversations.
  • Secure OAuth2 authentication.

use cases of Gmail MCP?

  1. Automating email management tasks.
  2. Integrating Gmail functionalities into applications.
  3. Customizing email workflows and settings.

FAQ from Gmail MCP?

  • Is Gmail MCP stable for production use?

This server is experimental and functionality is not guaranteed; use at your own risk.

  • How do I authenticate with Gmail MCP?

Follow the setup instructions to create OAuth credentials and run the authentication command.

  • Can I customize the credential file locations?

Yes, you can use environment variables to customize the paths for OAuth credentials.

Server Config

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": [
        "@shinzolabs/gmail-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shinzo-labs
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago