Google Services MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your OAuth client ID | |
| GOOGLE_MAPS_API_KEY | Yes | Your Google Maps API key | |
| GOOGLE_CLIENT_SECRET | Yes | Your OAuth client secret | |
| GOOGLE_REFRESH_TOKEN | Yes | Your refresh token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeC | Convert an address to coordinates |
| reverse-geocodeC | Convert coordinates to an address |
| places-searchC | Search for places using text query |
| get-directionsC | Get directions between two locations |
| distance-matrixC | Calculate travel distance and time between multiple origins and destinations |
| place-detailsC | Get detailed information about a specific place |
| finance-searchA | Search for stocks, indices, mutual funds, currencies, and futures using Google Finance. Use format 'SYMBOL:EXCHANGE'. Stocks: 'AAPL:NASDAQ', 'TSLA:NASDAQ'. ETFs/Index funds: 'SPY:NYSEARCA', 'VTI:NYSEARCA', 'QQQ:NASDAQ', 'VOO:NYSEARCA'. Crypto: 'BTC-USD', 'ETH-USD'. Note: Query 'SPY' (no exchange) returns market overview with S&P 500 related ETFs. |
| airports-searchC | Search for airport and flight information using Google Flights |
| gmail-send-emailC | Send an email using Gmail |
| gmail-read-emailsC | Read/list emails from Gmail with optional search query |
| gmail-get-emailC | Get a specific email by message ID |
| gmail-get-labelsB | Get all Gmail labels |
| calendar-create-eventC | Create a new calendar event. Current time: 1/3/2026, 11:25:51 AM |
| calendar-list-eventsC | List calendar events with optional filters |
| calendar-get-eventC | Get a specific calendar event by ID |
| calendar-update-eventC | Update an existing calendar event |
| calendar-delete-eventC | Delete a calendar event |
| calendar-list-calendarsB | List all available calendars |
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 18 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools are grouped by service (calendar, gmail, maps/geography, finance, flights) and each performs a specific action on a specific resource. For example, calendar tools handle events and calendars separately, while mapping tools cover geocoding, directions, and place searches without overlap.
Tool names follow a highly consistent service-action-resource pattern throughout. All tools use snake_case with clear prefixes (calendar-, gmail-, place-, etc.) followed by verb_noun combinations. This makes it easy to predict tool functionality and maintain readability across all 18 tools.
With 18 tools covering multiple Google services (Calendar, Gmail, Maps, Finance, Flights), the count is reasonable for the broad scope. It's slightly on the higher side but well-organized into logical groups. Each tool appears necessary for its domain, though some services have more coverage than others.
The tool set provides excellent coverage for the supported services with only minor gaps. Calendar and Gmail tools offer full CRUD operations, mapping tools cover essential geospatial functions, and finance/flights tools handle key queries. Minor gaps include no calendar event search beyond listing and no Gmail email deletion, but agents can work around these limitations effectively.