gmail_get_email_body_chunk
Get a 1k character chunk of an email body starting from the specified offset
LABSCO SUMMARY
Credentials travel with the call, so one server can act for whichever mailbox the caller holds a token for.
That is the decision to understand before installing it: no account is stored, the access token is in the arguments each time, and gmail_refresh_token exists to renew it partway through a long session. Reading is chunked at 1k characters by design — snippets and a first chunk from gmail_get_recent_emails, then one gmail_get_email_body_chunk call per further chunk — which keeps a big thread from arriving all at once but makes reading one long message several calls. Search, labels and delete are not part of the set; it covers recent mail, one body at a time, and sending.
What it is
A Gmail server that takes its Google OAuth credentials as tool arguments rather than from stored configuration, 4 tools covering token refresh, recent mail, body paging and sending.
What you get
- gmail_get_recent_emails returns metadata, snippets and the first 1k characters of each body, with max_results and an unread_only filter
- gmail_get_email_body_chunk returns a further 1k character chunk from a given offset, addressed by message_id or thread_id, for anything longer than that first slice
- gmail_send_email takes to, subject and either a plain body or an html_body
- gmail_refresh_token exchanges a refresh token and client credentials for a new access token without restarting the session
Requirements
Google OAuth credentials supplied per call: google_access_token on every tool, plus google_client_id, google_client_secret and google_refresh_token for gmail_refresh_token. MIT licensed.
Setup effort
One command — npx @peakmojo/mcp-server-headless-gmail
USE CASES
01
Catching up on what arrived while you were away
Pull recent messages with metadata, snippets and the first slice of each body, then page through the ones that are longer than that first slice, chunk by chunk.
02
Answering a message from inside the conversation
Find the message, read enough of the body to answer it properly, and send the reply as plain text or HTML without switching to a mail client.
03
Keeping a long session authenticated
When the access token in the arguments expires partway through, exchange the refresh token and client credentials for a new one and carry on with the same tools.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
gmail_get_recent_emails
Get the most recent emails from Gmail (returns metadata, snippets, and first 1k chars of body)
gmail_refresh_token
Refresh the access token using the refresh token and client credentials
gmail_send_email
Send an email via Gmail
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
- npx on PATH
- Python 3.10 or later
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-server-headless-gmail": {
"command": "npx",
"args": [
"@peakmojo/mcp-server-headless-gmail"
]
}
}
}npx
TERMINAL
npx @peakmojo/mcp-server-headless-gmail
