Skip to main content
Glama
sahildhurat

Google Workspace MCP Server

by sahildhurat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_TOKEN_PATHYesAbsolute path to the Google OAuth token JSON file
GOOGLE_CREDENTIALS_PATHYesAbsolute path to the Google OAuth credentials JSON file

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_emailB

Send an email immediately via the authenticated Gmail account.

draft_emailB

Create a draft in the authenticated Gmail account without sending.

append_to_google_docB

Append text content to the end of an existing Google Doc.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: append_to_google_doc targets Google Docs, while draft_email and send_email target Gmail with different actions (create draft vs send). No overlap exists between the three tools.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case: append_to_google_doc, draft_email, send_email. The pattern is predictable and uniform across the set.

Tool Count2/5

At 3 tools for a 'Google Workspace MCP Server,' the count feels too low. The server name suggests broader coverage of multiple Google Workspace services, but only Docs (append) and Gmail (draft/send) are represented, making the scope overly narrow.

Completeness1/5

The toolset is severely incomplete for Google Workspace. Key operations like creating or reading Google Docs, listing emails, managing labels, or handling attachments are missing. Agents cannot perform basic CRUD workflows for either Docs or Gmail.

Resources