Gmail Sender MCP Server

Created By
abhishekloiwala year ago
An MCP server for sending Gmail emails via Claude or other AI assistants
Overview

what is Gmail Sender MCP?

Gmail Sender MCP is a Model Context Protocol (MCP) server that enables AI assistants like Claude to send emails via the Gmail API. It focuses solely on email sending capabilities, allowing for both new emails and replies to existing emails.

how to use Gmail Sender MCP?

To use Gmail Sender MCP, set up the server by following the provided instructions, including creating a Google Cloud project, enabling the Gmail API, and configuring your credentials. Once set up, run the server and connect it to your AI assistant.

key features of Gmail Sender MCP?

  • Send new emails and reply to existing emails through AI assistants.
  • Lightweight and easy to set up using the Gmail API.
  • Supports HTML formatting in email content.

use cases of Gmail Sender MCP?

  1. Automating email responses for customer service.
  2. Sending notifications or alerts via email from AI applications.
  3. Integrating email functionalities into chatbots or virtual assistants.

FAQ from Gmail Sender MCP?

  • What are the prerequisites for using Gmail Sender MCP?

You need Python 3.8 or higher, a Google Cloud account with the Gmail API enabled, and optionally Docker for containerized deployment.

  • Is there a way to run this server in a Docker container?

Yes! You can build and run the server using Docker or Docker Compose.

  • How do I secure my credentials?

Keep your .env file secure and do not commit it to version control. Treat your refresh token like a password.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abhishekloiwal
Star
0
Language
Python
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