Generic Gmail & Google Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (e.g., info, debug, warn, error) | info |
| MCP_HTTP_HOST | No | Optional HTTP transport host | |
| MCP_HTTP_PATH | No | Optional HTTP transport path | |
| MCP_HTTP_PORT | No | Optional HTTP transport port | |
| MCP_HTTP_TOKEN | No | Optional access token for HTTP transport authentication | |
| GOOGLE_CLIENT_ID | Yes | Google OAuth 2.0 client ID | |
| GOOGLE_REDIRECT_URI | No | Google OAuth redirect URI, must match the authorized redirect URI in the Google Cloud console | http://localhost:3000/oauth2callback |
| GOOGLE_CLIENT_SECRET | Yes | Google OAuth 2.0 client secret | |
| GOOGLE_REFRESH_TOKEN | Yes | Google OAuth 2.0 refresh token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_email_draftA | Create a Gmail draft without sending it. Use this when the user wants to review or edit the message first. Requires to, subject, and body. Supports optional cc, bcc, htmlBody, threadId, and inReplyTo. |
| send_emailA | Send an email immediately through Gmail. Use this only when the user wants the message delivered now, not saved as a draft. Requires to, subject, and body. Supports optional cc, bcc, htmlBody, threadId, and inReplyTo. |
| append_to_google_docA | Append caller-supplied text to the end of an existing Google Doc. Does not create a document, generate content, or interpret markdown. Requires documentId and content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.