
Gmail
io.github.markswendsen-codePublished by GitHub account markswendsen-codev0.1.0Updated Oct 25, 2026
Gmail MCP server — send, read, and search email. By Strider Labs.
Overview
A local Gmail connector that lets an assistant send, search, list and read email from the user's own Google account.
- What you can do
- Send email from the user's Gmail account, with optional CC and BCC recipients and a subject and body supplied by the assistant or user. Search the mailbox using Gmail search syntax and cap the number of results. List recent inbox messages, optionally filtered by label such as INBOX or UNREAD. Read the full content of a specific message by its Gmail message ID.
- When to use it
- Useful when you want an assistant to triage incoming mail, look up past conversations, draft or send replies, or send messages on your behalf. Best for personal or small-team setups where one Gmail account is enough.
- Requirements
- Runs locally via npx, so Node.js is needed. Requires a Google Cloud project with the Gmail API enabled and OAuth 2.0 credentials: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and GOOGLE_REFRESH_TOKEN must be set in the client configuration. Network access to Google is required.
Installation
In SourceWeft
- Open Gmail in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@striderlabs/mcp-gmail
MCP server that gives AI agents the ability to send, read, and search email via Gmail.
For Agents
Agents use this connector to handle email autonomously on behalf of their human — reading important messages, searching for information, composing thoughtful replies, and sending communications.
Example agent workflows:
- Triage emails: Agent reads new messages, summarizes important ones, and flags urgent items for user attention
- Answer routine questions: Agent searches email history to find information, composes replies with context from past conversations
- Send on behalf: Agent drafts and sends professional emails based on user intent ("Let the team know I'll be late"), then logs a copy to the conversation
Usage example:
User: "Has anyone replied to my email about the Q2 budget proposal?"
Agent:
gmail_search→"to:me subject:budget"gmail_read→ Read each message- Return summary: "Sarah replied yes on Monday. Mark asked for revisions. No word from Finance yet."
Then agent might automatically draft a follow-up to Finance and ask for approval before sending.
Installation
Configuration
Add to your MCP client configuration (e.g., Claude Desktop):
Available Tools
gmail_send
Send an email from the user's Gmail account.
Parameters:
to(required): Recipient email addresssubject(required): Email subject linebody(required): Email body contentcc(optional): CC recipientsbcc(optional): BCC recipients
gmail_search
Search emails using Gmail search syntax.
Parameters:
query(required): Gmail search query (e.g., "from:[email protected]")maxResults(optional): Maximum results (default: 10)
gmail_read
Read the full content of a specific email.
Parameters:
messageId(required): The Gmail message ID
gmail_list
List recent emails from the inbox.
Parameters:
maxResults(optional): Maximum emails to list (default: 10)label(optional): Filter by label (e.g., "INBOX", "UNREAD")
Getting Google OAuth Credentials
- Go to Google Cloud Console
- Create a new project or select existing
- Enable the Gmail API
- Create OAuth 2.0 credentials
- Use the OAuth playground or your app to get a refresh token
Response Format
All tools return structured JSON:
Part of Strider Labs
Strider Labs builds action execution infrastructure for AI agents.
- Website: https://striderlabs.ai
- GitHub: https://github.com/striderlabs
License
MIT
Source: README.md at commit 0d8196d
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.