Mariana Google MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Google OAuth 2.0 client ID (e.g., your-client-id.apps.googleusercontent.com) | |
| GOOGLE_CLIENT_SECRET | Yes | Google OAuth 2.0 client secret |
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 |
|---|---|
| google_authA | Authenticate a Google account. Opens a browser for OAuth consent. Use this to add a new account or re-authenticate an existing one. |
| google_statusA | Check connection health for all configured Google accounts. Shows token status and last action. |
| gmail_searchA | Search Gmail messages. Uses Gmail search syntax (e.g. 'from:name subject:topic'). |
| gmail_readA | Read a specific Gmail message by ID. Returns full message content. |
| gmail_list_labelsB | List all Gmail labels/folders for an account. |
| gmail_draftA | Create a draft email. Does NOT send — the draft appears in Gmail for manual review and sending. |
| gmail_move_to_deleteA | Soft-delete: move messages to a 'To Be Deleted' label. Does NOT delete or trash messages. |
| calendar_listB | List upcoming calendar events. |
| calendar_searchC | Search calendar events by keyword. |
| calendar_getA | Get full details of a specific calendar event. |
| calendar_createA | Create a calendar event. Does NOT send invites by default. |
| calendar_updateA | Modify an existing calendar event. Does NOT notify attendees by default. |
| calendar_flag_deleteA | Soft-delete: prepend 'DELETE - ' to event title. Does NOT actually delete the event. |
| calendar_availabilityC | Check free/busy status for a date or date range. |
| contacts_searchB | Search Google Contacts by name, email, or phone number. |
| contacts_listC | List Google Contacts, optionally filtered by contact group. |
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 16 tools
Tools are cleanly separated by domain (calendar_, contacts_, gmail_, google_) with distinct actions within each domain. No overlapping functionality between tools like calendar_flag_delete and gmail_move_to_delete, as prefixes clearly indicate target services.
Consistent snake_case throughout with clear resource_action pattern (e.g., calendar_create, gmail_read, contacts_search). All 16 tools follow the same naming convention without mixing styles or verb forms.
16 tools is slightly above the ideal 3-15 range but reasonable given it covers three distinct Google services (Calendar, Gmail, Contacts) plus authentication. Each tool serves a specific purpose without redundancy.
Calendar has strong CRUD coverage (create, get, update, list, search, soft-delete). Gmail covers reading, drafting, and soft-delete but lacks send functionality (by design). Contacts is notably incomplete with only read operations (list/search) and no create, update, or delete capabilities.