Gmail IMAP MCP Server

Created By
tonykipkemboia year ago
Gmail IMAP MCP server for integrating Gmail with Claude and other AI assistants
Overview

What is Gmail IMAP MCP Server?

The Gmail IMAP MCP Server is a Model Context Protocol (MCP) server designed for integrating Gmail with AI assistants, allowing them to read, search, and manage emails through IMAP.

How to use Gmail IMAP MCP Server?

To use the server, clone the repository, set up a Google Cloud project with the Gmail API enabled, and authenticate your Gmail account using OAuth2. Start the server and use the provided tools to interact with your Gmail account.

Key features of Gmail IMAP MCP Server?

  • OAuth2 authentication with Gmail
  • Read and search emails with advanced options
  • Send emails with attachments
  • Manage labels (create, delete, list)
  • Support for multiple Gmail accounts
  • Integration with AI assistants through MCP

Use cases of Gmail IMAP MCP Server?

  1. Automating email management tasks for users.
  2. Enabling AI assistants to summarize and triage emails.
  3. Facilitating email composition and organization through voice commands.

FAQ from Gmail IMAP MCP Server?

  • Can I use this server with multiple Gmail accounts?

Yes, the server supports multiple Gmail accounts.

  • Is there a limit on the number of emails I can manage?

No, but performance may vary based on the number of emails and server resources.

  • How secure is my data with this server?

OAuth2 credentials are stored securely, and the server uses secure connections to Gmail.

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

a day ago
Crevio

2 days ago