Gmail Server for Model Context Protocol (MCP)

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Gmail Server for Model Context Protocol (MCP)?

This project is a server that integrates with Gmail to enable functionalities such as sending, removing, reading, drafting, and responding to emails through the Model Context Protocol (MCP).

how to use Gmail Server for MCP?

To use this server, set up the Gmail API, authenticate your application, and configure it to work with an MCP client. Follow the setup instructions provided in the documentation.

key features of Gmail Server for MCP?

  • Send emails to specified recipients.
  • Remove emails by moving them to trash.
  • Mark emails as read.
  • Retrieve unread emails.
  • Read specific email content.
  • Open emails in a browser.

use cases of Gmail Server for MCP?

  1. Automating email responses in applications.
  2. Integrating email functionalities into desktop applications.
  3. Managing email workflows programmatically.

FAQ from Gmail Server for MCP?

  • Can this server send emails on behalf of the user?

Yes, it can send emails after user authentication.

  • Is there a limit to the number of emails that can be processed?

The limits depend on Gmail's API usage policies.

  • How do I troubleshoot issues with the server?

Use the MCP Inspector tool for testing and troubleshooting.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

2 hours 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)

a day ago