Feature Request: Add gmail_send_draft / gmail_send_message tool to Gmail MCP connector

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The current Gmail MCP connector workflow requires me to manually open Gmail
to send emails. When using Claude Code to automate tasks like sending AI-generated
digests, newsletters, or reports, I can only create a draft — there is no tool
to actually send it. This breaks fully automated email workflows.The current Gmail MCP connector workflow requires me to manually open Gmail
to send emails. When using Claude Code to automate tasks like sending AI-generated
digests, newsletters, or reports, I can only create a draft — there is no tool
to actually send it. This breaks fully automated email workflows.

Proposed Solution

Add one (or both) of the following tools to the Gmail MCP connector:

1. gmail_send_draft — accepts a draftId and sends the existing draft
2. gmail_send_message — sends an email directly without a prior draft step

The ideal experience: after calling gmail_create_draft, I can immediately
call gmail_send_draft with the returned draftId to complete the send
in the same workflow.

Alternative Solutions

Currently working around this by saving a draft and manually opening Gmail
to click Send. Also considered using a self-hosted Gmail MCP server that
includes send functionality, but that adds unnecessary complexity for
something the official connector should support natively.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

Example scenario:

1. I ask Claude to research today's top AI news and compile a digest
2. Claude formats and calls gmail_create_draft with the content
3. Currently I must stop and manually go to Gmail to send it
4. With gmail_send_draft, Claude could complete the full workflow

autonomously — research → format → send — without manual steps

Additional Context

The draftId returned from gmail_create_draft (e.g. r-519844011788993847)
is already available in the tool response, so the implementation simply
needs to call the Gmail API's drafts.send endpoint with that ID.
The Gmail API already supports this natively.

Reference: https://developers.google.com/gmail/api/reference/rest/v1/users.drafts/send