Gmail MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Gmail MCP Server?

Gmail MCP Server is a powerful and flexible integration server built using the MCP (Message Control Protocol) framework, designed to interact with Gmail APIs for programmatic email management.

how to use Gmail MCP Server?

To use the Gmail MCP Server, install it via Smithery, set up a Google Cloud Project with Gmail API enabled, and configure your email accounts. Start the server and use the provided tools to read, send, and manage emails.

key features of Gmail MCP Server?

  • Read emails from multiple Gmail accounts
  • Send emails with attachments
  • Search emails with advanced query options
  • Download email attachments
  • Handle email conversations and threads
  • Real-time email monitoring

use cases of Gmail MCP Server?

  1. Automating email responses for customer support.
  2. Integrating email functionalities into applications.
  3. Monitoring and managing multiple Gmail accounts programmatically.

FAQ from Gmail MCP Server?

  • What are the prerequisites to run the server?

You need Python 3.12 or higher, a Google Cloud Project with Gmail API enabled, and OAuth 2.0 credentials.

  • Is there a way to handle multiple Gmail accounts?

Yes! The server supports multiple Gmail accounts and allows you to manage them programmatically.

  • How do I secure my credentials?

Store your client_secret.json securely, use environment variables for sensitive information, and regularly rotate your OAuth credentials.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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)

2 days ago