Skip to main content
Glama
epaproditus

Google Workspace MCP Server

by epaproditus

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_CLIENT_IDYesYour Google OAuth client ID from the Google Cloud Console
GOOGLE_CLIENT_SECRETYesYour Google OAuth client secret from the Google Cloud Console
GOOGLE_REFRESH_TOKENYesOAuth refresh token obtained through the get-refresh-token.js script

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_emailsB

List recent emails from Gmail inbox

search_emailsC

Search emails with advanced query

send_emailC

Send a new email

modify_emailA

Modify email labels (archive, trash, mark read/unread)

list_eventsC

List upcoming calendar events

create_eventC

Create a new calendar event

update_eventB

Update an existing calendar event

delete_eventB

Delete a calendar event

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation5/5

Tools are clearly separated into two domains: calendar (create/delete/list/update events) and email (list/search/send/modify labels). No overlapping purposes, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow an excellent verb_noun pattern (e.g., create_event, list_emails). There is no mixing of conventions or inconsistent verb styles.

Tool Count5/5

With 8 tools, the set is well-scoped for covering two major Google Workspace services. Neither too few nor too many, each tool serves a distinct purpose.

Completeness4/5

Calendar operations are complete (CRUD). Email operations cover list, search, send, and label modification, but are missing permanent deletion and the ability to fetch detailed content of a single email. Still, core workflows are well-covered.

Maintenance

ActivityInactive
ResponsivenessNo issues