What Gmail OAuth scopes are required?
The server uses `https://www.googleapis.com/auth/gmail.modify` which allows reading, sending, and modifying emails.
@MCP-Mirror
Basic information
Mirror of
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"jasonsum_gmail-mcp-server": {
"command": "npx",
"args": [
"@modelcontextprotocol/inspector",
"uv",
"run",
"[absolute-path-to-git-repo]/src/gmail/server.py",
"--creds-file-path",
"[absolute-path-to-credentials-file]",
"--token-path",
"[absolute-path-to-access-tokens-file]"
]
}
}
}Sends email to email address recipient
Moves email to trash
Marks email as read
Retrieves unread emails
Retrieves given email content
Open email in browser
This MCP server integrates with Gmail to enable sending, removing, reading, drafting, and responding to emails. The MCP client prompts the user before conducting such activities.
First, set up a Google Cloud project, enable the Gmail API, configure an OAuth consent screen with test user, add OAuth scope https://www.googleapis.com/auth/gmail/modify, and create an OAuth Client ID for a Desktop App. Download the JSON credentials file and note its absolute path. Then configure an MCP client (e.g., Claude Desktop) using uv with parameters --creds-file-path and --token-path. On startup, a browser-based authentication flow saves token credentials to the specified token path.
The server uses `https://www.googleapis.com/auth/gmail.modify` which allows reading, sending, and modifying emails.
On server start, a browser-based OAuth flow launches. Token credentials are saved to the file specified by `--token-path` and reused on subsequent runs.
A Google Cloud project with the Gmail API enabled, a Desktop App OAuth client, and `uv` for running the server. No Python dependencies beyond those bundled with the server are mentioned.
Credentials are stored in the file path given to `--creds-file-path`. Access and refresh tokens are stored in the file path given to `--token-path`. Both are local file paths on the user’s machine.
The server is run via `uv run gmail --creds-file-path <path> --token-path <path>`. It communicates over stdio (standard MCP transport).

Send, receive and track real faxes in the US and Canada from Claude, ChatGPT or Cursor.

AI call analysis and voice agents for sales teams. This MCP server lets a team's own AI assistant read minute usage, agents, call summaries and daily stats, look up caller history, schedule consent-gated AI callbacks, an
Mektup gives AI agents and their humans a real email mailbox, not just a one-way sending API. Through 41 MCP tools, an agent can register a domain, create a mailbox, send and receive mail, and manage threads, drafts, fol

Agencies and GTM teams use HeyReach and Instantly to run LinkedIn outbound from personal sender profiles — but those profiles sit empty and prospects don't accept. B2B Creators is the content layer that keeps every sende
LinkedIn MCP server for Claude, ChatGPT, Cursor & Codex. Read LinkedIn DMs, search your network, enrich profiles and draft messages you review before sending.
Comments