gmail-mcp-server
Provides tools for composing Gmail drafts, allowing users to create email drafts with optional recipient and plain-text body that the owner reviews and sends manually.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gmail-mcp-server Draft an email to myself about the Q3 budget review"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gmail-mcp-server
Standalone Gmail MCP Server — draft-only. Lane never sends; the single tool creates a Gmail draft the owner reviews and sends themselves.
Tools
gmail_draft_compose
Creates a Gmail draft.
Arg | Type | Required | Notes |
| string | no | Falls back to |
| string | no | Leave empty if unknown — the owner fills it in when reviewing the draft |
| string | yes | |
| string | yes | Plain text |
Returns { draftId, messageId, draftUrl }.
There is no send tool, no read tool, and no label/thread management in this server — it composes drafts only.
Related MCP server: AVA
Install / Dev
npm install
npm run dev # run the server via tsx
npm run build # compile to dist/
npm run check # test + buildAuth
Requires an OAuth 2.0 access token with the gmail.compose scope only — never gmail.send. Set it via GMAIL_ACCESS_TOKEN or pass accessToken per call. See .env.example.
Available Tools
1 toolgmail_draft_composeA
Create a Gmail draft. Draft-only — this server has no send capability. The owner reviews the draft in Gmail and sends it themselves.
Inputs: body (required), subject (required), to, accessToken.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clearly stated.
The single tool name follows a clear verb_noun pattern (gmail_draft_compose), but with only one tool there is limited evidence of a broader convention. It is readable and predictable.
A single tool for a Gmail server is far too thin to be useful. The server's apparent scope is much broader than drafting, and one tool cannot reasonably cover it.
The surface is severely incomplete. There is no send, read, list, search, or delete capability, and the tool only creates drafts, leaving the agent with a dead end after composing.
Maintenance
Related MCP Connectors
Manage Gmail end-to-end: search, read, send, draft, label, and organize threads. Automate workflow…
Manage Gmail messages, threads, labels, drafts, and settings from your workflows. Send and organiz…
Email inboxes for AI agents: send, reply, read verification codes, human-approved drafts.
Email inboxes and calendars for AI agents: send, receive, search, draft and schedule.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with Gmail through the Gmail API, allowing users to list, read, search emails, create and send drafts, and get email summaries through natural language commands with OAuth2 authentication.-
- AlicenseCqualityDmaintenanceEnables AI agents to create Gmail drafts safely using the Gmail API, without sending emails.11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create Gmail drafts and append content to Google Docs, supporting automated review analysis and notification workflows.537 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to create, list, update, and delete Microsoft 365 email drafts, with a hard guarantee that no message can be sent automatically, ensuring human review before any email goes out.1241 PyPIMIT