Google Workspace Code MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_WORKSPACE_TOKEN | No | Path to the stored OAuth token. Defaults to '~/.pi/google-workspace/token.json'. | |
| GOOGLE_WORKSPACE_AUTH_MODE | No | Authentication mode, either 'cloud' or 'local'. Defaults to 'cloud'. | cloud |
| GOOGLE_WORKSPACE_CLIENT_ID | No | The Google Workspace Client ID. | |
| GOOGLE_WORKSPACE_CONFIG_DIR | No | The configuration directory for Google Workspace. Defaults to '~/.pi/google-workspace'. | |
| GOOGLE_WORKSPACE_CREDENTIALS | No | Path to or content of Google Workspace credentials. | |
| GOOGLE_WORKSPACE_CALLBACK_HOST | No | The host used for the OAuth callback flow. | |
| GOOGLE_WORKSPACE_CLOUD_FUNCTION_URL | No | The URL for the Google Workspace Cloud Function. |
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 |
|---|---|
| executeB | Execute JavaScript/TypeScript inside a Node vm context with authenticated Google Workspace access. TypeScript type syntax is stripped before execution. The script runs inside an async function body and can use: auth, google, workspace, state. Return values with |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clearly defined purpose: executing JavaScript/TypeScript code in a Google Workspace context.
A single tool inherently has perfect naming consistency. The tool name 'execute' follows a clear verb-based pattern, and there are no other tools to create inconsistency.
One tool is too few for a server with the broad scope implied by 'Google Workspace Code MCP'. This suggests a single-purpose utility rather than a comprehensive interface to Google Workspace, which typically involves multiple resources and operations.
The tool set is severely incomplete for the stated purpose. A Google Workspace integration would typically require tools for managing users, groups, documents, calendars, etc., but this server only provides a generic code execution tool with no specific Workspace operations.