Three capabilities, all read: search, list, fetch. Nothing sends, deletes or labels, which makes the OAuth grant easier to reason about than a full-access mail integration. The cost is the setup — you build the Google Cloud OAuth client yourself, which is a few console screens before the first query.
A read-only MCP server over the Gmail API. You create your own OAuth client in Google Cloud, authorize it once from the command line, and the server uses the resulting token to answer questions about your mailbox.
- Emails found by a search — the same queries you would type into Gmail, such as everything from one sender
- The full content of one message pulled back, addressed by its subject or the search that found it
- Recent messages from the inbox listed, with a count you choose
Your own Google Cloud project with the Gmail API enabled and a Desktop-application OAuth client; download the credentials JSON and save it as `credentials.json`. Authorize once with `uv run gmail-mcp auth --creds-path credentials.json --token-path token.json`, which opens a browser and writes `token.json`. Point the server at both files through `GMAIL_CREDS_PATH` and `GMAIL_TOKEN_PATH`, and run it with `uvx --from git+https://github.com/vinayak-mehta/gmail-mcp gmail-mcp`. The package is `gmail-mcp` 0.1.0.
One command plus a key — uvx --from git+https://github.com/vinayak-mehta/gmail-mcp gmail-mcp, then supply credentials