Gmail MCP Server

Created By
christo707a year ago
Gmail MCP Server using Java and Spring Boot
Overview

what is Gmail MCP Server?

Gmail MCP Server is a Spring Boot application that implements the Model Context Protocol (MCP) for Gmail, allowing users to interact with their Gmail accounts programmatically.

how to use Gmail MCP Server?

To use the Gmail MCP Server, clone the repository, configure your Gmail API credentials, build the project using Maven, and run the server. You can also test the server functionality using the provided ClientStdio client.

key features of Gmail MCP Server?

  • GMailer Tools: Functions to manage emails such as sending, reading, marking as read, and moving to trash.
  • ClientStdio: A client for testing the MCP server functionality via standard input and output.

use cases of Gmail MCP Server?

  1. Automating email management tasks like sending and organizing emails.
  2. Building applications that require email notifications or interactions.
  3. Testing and developing features that integrate with Gmail.

FAQ from Gmail MCP Server?

  • What are the prerequisites for running the server?

You need Java 17 or higher, Maven, and Gmail API credentials.

  • Is there a client provided for testing?

Yes, the ClientStdio class is included for testing the MCP server functionality.

  • What license is the project under?

The project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
christo707
Star
0
Language
Java
License
MIT 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