Google Workspace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (default: info) | |
| MCP_API_KEY | No | API key for authenticating MCP clients (required for HTTP mode) | |
| GOOGLE_SCOPES | No | Override default scopes. Default scopes: https://www.googleapis.com/auth/gmail.compose, https://www.googleapis.com/auth/documents | |
| GOOGLE_CLIENT_ID | No | Google OAuth client ID | |
| ENABLE_OAUTH_SETUP | No | Set to true to enable OAuth setup endpoint temporarily | |
| GOOGLE_REDIRECT_URI | No | OAuth redirect URI, e.g., http://localhost:3000/oauth2callback | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret | |
| GOOGLE_REFRESH_TOKEN | No | Google OAuth refresh token (alternative to token storage for HTTP mode) | |
| GOOGLE_TOKEN_STORAGE | No | Path to store Google OAuth tokens, e.g., .tokens/google-token.json |
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 |
|---|---|
| gmail_create_draftA | Create a draft email in the authenticated user's Gmail account without sending it. When to use:
Required parameters: to (non-empty array of valid emails), subject, body. Optional: cc, bcc, is_html (default false). Side effects: Creates a Gmail draft only. Does not send the email. Success: Returns draft_id, message_id, thread_id, and provider "gmail". Common failures: VALIDATION_ERROR (bad emails/missing fields), AUTHENTICATION_REQUIRED, AUTHORIZATION_DENIED, GOOGLE_API_ERROR. |
| gmail_send_emailA | Send an email through Gmail on behalf of the authenticated Google account. IMPORTANT SIDE EFFECT: This tool actually sends an email. It is not a draft. MCP clients/agents should obtain user confirmation when appropriate before calling this tool. The server will not silently convert a send into a draft. When to use:
Required parameters: to (non-empty array of valid emails), subject, body. Optional: cc, bcc, is_html (default false), idempotency_key (reserved; not enforced in v1 — sends are not inherently idempotent). Success: Returns message_id, thread_id, and provider "gmail". Common failures: VALIDATION_ERROR, AUTHENTICATION_REQUIRED, AUTHORIZATION_DENIED, RATE_LIMITED, GOOGLE_API_ERROR, NETWORK_ERROR. Recipient addresses and content are not silently modified. |
| google_docs_append_contentA | Append plain text to the end of an existing Google Doc. When to use:
Required parameters: document_id, content (non-empty). Optional: add_newline_before (default true), add_newline_after (default false). Side effects: Mutates the document body by inserting text at the end of the body segment. Uses revision WriteControl so concurrent edits are detected rather than applied blindly. Success: Returns document_id, appended_characters, and provider "google_docs". Common failures: VALIDATION_ERROR (empty content), RESOURCE_NOT_FOUND, AUTHENTICATION_REQUIRED, AUTHORIZATION_DENIED, GOOGLE_API_ERROR (including stale revision). |
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: creating a Gmail draft, sending a Gmail email, and appending to a Google Doc. The descriptions explicitly contrast draft vs. send and provide strong guidance on when to use each, eliminating misselection risk.
All tool names use consistent snake_case with a service prefix + verb + noun pattern: gmail_create_draft, gmail_send_email, google_docs_append_content. The only minor deviation is the prefix style (gmail vs google_docs), but this is still readable and predictable.
Three tools is very thin for a server labeled 'Google Workspace,' which implies broad coverage of Gmail, Docs, Drive, Calendar, and more. While the individual tools are well-scoped, the count is mismatched to the apparent breadth of the stated purpose.
The surface covers only Gmail draft/send and Docs append, with no read, list, search, update, or delete operations for those services, and no other Workspace products at all. This leaves significant gaps that would cause agent dead ends for common Workspace tasks.