You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
gog-mcp: expose gmail drafts.send operation + grant for approved client sends #273
gog-mcp exposes no way to send an existing Gmail draft. capabilities_describe google_gmail_users_drafts_send returns forbidden_operation: operation is not available, and the account grants are drive.read, gmail.read, gmail.write with no send grant. The only send path is mail_compose_send, which composes a new message and so cannot send a reviewed draft unchanged.
Impact
Three client drafts approved by the account owner on 2026-10-08 could not be sent through MCP. They were sent through the gog CLI fallback (gog gmail drafts send) under a one-off exception.
Requested
Expose a gmail drafts.send operation in the MCP catalog that sends an existing draft ID unchanged.
Add a distinct send grant and write gate for it, so approved client sends are explicit and auditable.
Return the sent message ID and thread ID for readback.
Acceptance
With the grant, drafts.send sends the draft unchanged and returns IDs.
Without the grant it fails with a typed permission error.
Contract tests in internal/mcpcontract cover both cases.
GitHub sweep 2026-10-12, held for Jeremy: gmail.users.drafts.send is already in the pinned catalog (google_gmail_users_drafts_send). The forbidden_operation you saw comes from caller allow_operations and grants, not missing code. Letting an agent principal send client mail is a client-facing send approval. That is your decision: grant it as config, or add a dedicated send gate first, as this issue's acceptance criteria ask.
Activity
itsjeremyjohnson commentedon Oct 12, 2026
GitHub sweep 2026-10-12, held for Jeremy:
gmail.users.drafts.sendis already in the pinned catalog (google_gmail_users_drafts_send). Theforbidden_operationyou saw comes from caller allow_operations and grants, not missing code. Letting an agent principal send client mail is a client-facing send approval. That is your decision: grant it as config, or add a dedicated send gate first, as this issue's acceptance criteria ask.itsjeremyjohnson commentedon Oct 12, 2026
Parked (sweep 2026-10-12): enabling this needs new write or publish scopes and grants on the deployed gog-mcp, which is an auth change.