Gmail + Google Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port the HTTP transport binds to (only when MCP_TRANSPORT=http) | 8080 |
| LOG_LEVEL | No | Structured JSON log verbosity: trace|debug|info|warn|error|fatal | info |
| MCP_TRANSPORT | No | Transport type: stdio or http | stdio |
| MCP_AUTH_TOKEN | No | Shared secret remote clients must send as Bearer token (required if MCP_TRANSPORT=http) | |
| MCP_SERVER_NAME | No | Name this server reports over MCP | google-workspace-mcp-server |
| GOOGLE_CLIENT_ID | Yes | OAuth client ID from Google Cloud Console | |
| ENABLE_HTML_EMAIL | No | If false, gmail_create_draft/gmail_send_email reject isHtml: true | true |
| ENABLE_DOCS_APPEND | No | If false, the docs_append_text tool is not registered | true |
| GOOGLE_REDIRECT_URI | No | Redirect URI used for the one-time authorize flow | http://localhost:3000/oauth2callback |
| GOOGLE_CLIENT_SECRET | Yes | OAuth client secret from Google Cloud Console | |
| MAX_ATTACHMENT_BYTES | No | Max size per email attachment in bytes | 20971520 |
| MAX_CONFLICT_RETRIES | No | Retry attempts for docs_append_text when a concurrent edit is detected | 3 |
| TOKEN_ENCRYPTION_KEY | No | Base64, 32-byte key to encrypt token storage (auto-generated if unset) | |
| RATE_LIMIT_PER_MINUTE | No | Max calls allowed per tool per rolling 60s window | 60 |
| ALLOWED_GOOGLE_ACCOUNTS | No | Comma-separated email allowlist (not yet enforced) | |
| GOOGLE_TOKEN_STORAGE_PATH | No | Where the access/refresh token is stored | ./tokens.json |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to a service-account key file (reserved for future use) |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rohinigowdaiah1111/MCP-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server