Skip to main content
Glama
vbj2pxgs4j-cmd

google-tools-mcp-server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_CLIENT_IDYesYour Google OAuth Client ID.
GOOGLE_CLIENT_SECRETYesYour Google OAuth Client Secret.
GOOGLE_REFRESH_TOKENYesYour Google OAuth refresh token, generated via the auth:token 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
gmail_send_emailA

Sends an email directly to specified recipients via the user's Gmail account.

gmail_create_draftA

Creates an email draft in the user's Gmail account without sending it immediately. Allows human review before dispatch.

gdocs_append_contentB

Appends formatted or plain text content to the end of a specified Google Document.

gdocs_get_document_infoA

Retrieves document title, character count, and revision metadata to confirm access before modifying.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinct resource (Gmail vs Google Docs) and action (send, draft, append, get info). There is minor potential confusion between sending and drafting an email, but their descriptions clearly differentiate immediate dispatch from human review.

Naming Consistency4/5

Tool names follow a consistent pattern of <service>_<verb>_<object>, such as gmail_send_email and gdocs_append_content. Minor inconsistency: gdocs_get_document_info uses 'get_document_info' instead of a clearer 'get_info', but overall the pattern is predictable.

Tool Count4/5

With only 4 tools, the count feels slightly thin for a server covering two major Google services (Gmail and Docs). However, the tools are focused on essential workflows and each serves a distinct purpose, justifying its inclusion.

Completeness3/5

The server covers basic email creation (send and draft) and document interaction (append and get info). Notably missing are operations like reading emails, searching documents, or creating documents, which are common in such workflows and may cause agents to hit dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues