Generic Gmail & Google Docs MCP Server
Related Servers
Alternatives to Generic Gmail & Google Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables creating and sending Gmail drafts and appending content to Google Docs through MCP tools.334 npmMIT
- AlicenseBqualityDmaintenanceExposes Gmail (send/draft) and Google Docs (append) capabilities as tools for any MCP-compliant agent.344 npmISC
- FlicenseBqualityCmaintenanceEnables sending emails, drafting emails, and appending text to Google Docs via MCP tools.3-
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to create drafts and send emails in Gmail, and append text to existing Google Docs documents.-
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI agents to draft and send Gmail emails and append content to Google Docs without needing to understand Google's APIs.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send and draft Gmail emails and append content to Google Docs through standardized MCP tools.10 npmMIT
TDQS
Scored across 3 tools
The three tools target clearly distinct actions: appending to a Doc, saving a Gmail draft, and sending an email immediately. The draft-vs-send descriptions explicitly disambiguate the two email tools, and the Docs tool is orthogonal.
All names use snake_case with a leading verb (append_to_google_doc, create_email_draft, send_email), which is predictable and readable. Minor deviation in pattern shape (append_to_X vs create_X_draft vs send_X) keeps it from being perfectly uniform.
Three tools is thin for a server explicitly spanning two products (Gmail and Google Docs). While each tool earns its place, the surface is borderline for the stated multi-service scope.
Major gaps: no way to read, list, or search Gmail messages, no label/thread management, and for Docs only an append operation exists with no create, read, or fetch-content capability. This creates dead ends for common workflows.