MCP Google Workspace 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) | |
| MCP_SERVER_HOST | No | Host for the MCP server (default: localhost) | |
| MCP_SERVER_PORT | No | Port for the MCP server (default: 3000) | |
| GOOGLE_CLIENT_ID | Yes | Your Google OAuth client ID | |
| GOOGLE_REDIRECT_URI | Yes | OAuth redirect URI (e.g., http://localhost:3000/oauth/callback) | |
| GOOGLE_CLIENT_SECRET | Yes | Your Google OAuth client secret | |
| GOOGLE_TOKEN_STORAGE | Yes | Path to store 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 | Creates an email draft in the authenticated user's Gmail account. Use this tool when you want to prepare an email for review before sending. This tool does NOT send the email — the draft is only saved to Gmail Drafts. To send an email, use the gmail_send_email tool instead. |
| gmail_send_emailA | Sends an email immediately via the authenticated Gmail account. Use this tool only when the user has explicitly confirmed they want to send the email. WARNING: This action is PERMANENT — the email will be delivered immediately and cannot be recalled. To create a draft for review instead, use gmail_create_draft. |
| google_docs_append_contentA | Appends plain text content to the end of an existing Google Document. Use this tool to add new content at the bottom of a Google Doc without modifying existing content. The document ID can be found in the Google Doc URL: docs.google.com/document/d//edit Existing document content is never overwritten or deleted. |
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
Each tool targets a distinct action and resource: Gmail draft creation, Gmail sending, and Docs appending. The draft/send distinction is explicitly explained in both descriptions, so there is no real ambiguity.
All tool names follow a consistent snake_case service_verb_noun pattern: gmail_create_draft, gmail_send_email, google_docs_append_content. The naming makes the target service and action predictable.
Three tools is on the thin side for a server claiming to cover Google Workspace. The scope is limited to outbound Gmail actions and one Docs mutation, which feels under-scoped for the stated domain.
The tool surface is severely incomplete for Google Workspace: there is no way to read or search Gmail, create or update Google Docs, or access Calendar, Drive, Sheets, or other core Workspace services. It only supports writing outbound email and appending to existing docs, leaving agents unable to perform basic lifecycle operations.