Gmail MCP Server

Created By
aniket-raskar1a year ago
Overview

What is Gmail MCP Server?

The Gmail MCP Server is a Python-based package that integrates Gmail and Google Calendar with Claude Desktop, allowing users to manage their emails and calendar events through natural language commands.

How to use Gmail MCP Server?

To use the Gmail MCP Server, install the package via pip, ensure you have the necessary prerequisites, and run it as a background server to interact with your Gmail and Google Calendar.

Key features of Gmail MCP Server?

  • Email summarization for recent emails.
  • Sending emails directly from Claude Desktop.
  • Creating calendar events for important emails.
  • Automatic scheduling of calendar events based on email importance.
  • Secure authentication using OAuth 2.0.
  • Cross-platform support for Windows, macOS, and Linux.

Use cases of Gmail MCP Server?

  1. Automating email management tasks.
  2. Streamlining event scheduling based on email content.
  3. Enhancing productivity by using natural language commands to interact with Gmail and Google Calendar.

FAQ from Gmail MCP Server?

  • What are the prerequisites for using the Gmail MCP Server?

You need Python 3.8 or higher, Claude Desktop, a Google Cloud Project with the necessary APIs enabled, and a Gmail account.

  • Is the Gmail MCP Server free to use?

Yes, it is free to use as it is an open-source project.

  • How does the server ensure secure access to Gmail?

It uses OAuth 2.0 for secure authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aniket-raskar1
Star
1
Language
Python
License
-

Recommend Servers

View All
Alloy

2 days ago
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)

12 hours ago
Crevio

a day ago