Headless Gmail Server

Example Use Cases

• 1

  Read recent Gmail messages (id, threadId, from/to/subject/date and the first 1k of the body) in a headless or containerized environment without local OAuth storage.

• 2

  Retrieve full email bodies incrementally in 1k chunks (using offset) to handle very large messages or stream content.

• 3

  Send emails via Gmail and manage access/refresh token rotation decoupled from the server implementation.

Description

This MCP server provides Gmail read and send capabilities via simple tools: fetch recent emails (first 1k of body), retrieve full bodies in 1k chunks, send messages, and refresh access tokens. It is designed to run headless (Docker or npm) so clients can supply credentials as context, decoupling credential storage from the server. The server supports automatic token refreshing and a dedicated refresh tool to simplify OAuth flows for remote agents.

Capabilities(4 total)