google-nice-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_NICE_TOKEN | No | Cached token path. | <config>/token.json |
| GOOGLE_NICE_CONFIG_DIR | No | Where credentials/token live. | ~/.config/google-nice-mcp |
| GOOGLE_NICE_CREDENTIALS | No | OAuth client file path. | <config>/credentials.json |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gmail_searchA | Search your Gmail and return a compact list of matching emails. Filter by any combination of: a free-text keyword (matches anywhere), a sender email/name, words in the subject, and a date range. Dates use dd.mm.yyyy (e.g. 31.12.2026). 'after' means on/after that day, 'before' means before that day. With NO filters, returns your most recent emails. Returns id, from, subject, date and a short snippet for each hit. Use the id with gmail_read_email to read the full message. |
| gmail_read_emailA | Read one full email by its id (from gmail_search). Returns headers, the plain-text body, and the names of any attachments. |
| drive_searchA | Search Google Drive (your files and shared drives) and list matches. Filter by words in the file name, words found inside the file content (full-text), and/or file_type. Valid file_type values: doc, sheet, slides, pdf, folder. With NO filters, returns your most recently modified files. Set include_shared_drives=False to limit to your own Drive. Returns id, name, type, owner and last-modified time. Use the id with drive_read_file to read the contents. |
| drive_read_fileA | Read the text content of a Drive file by its id (from drive_search). Handles Google Docs, Sheets and Slides (exported to text/CSV) as well as PDF, Word (.docx), Excel (.xlsx) and PowerPoint (.pptx) files. Long files are truncated to max_chars; raise it to read more. |
| drive_list_shared_drivesA | List the shared drives you can access (id and name). Useful for discovering where project files live before searching. |
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 5 tools
Tools are clearly separated by service prefix (drive_ vs gmail_) and have distinct purposes: listing drives, searching and reading files, searching and reading emails. No overlap in functionality.
All tools follow a service_verb[_object] pattern with underscores, but some use a bare verb (drive_search, gmail_search) while others include an object (drive_list_shared_drives, drive_read_file, gmail_read_email). Slight inconsistency but the pattern is predictable.
With 5 tools covering two Google services, the count is well-scoped. Each tool serves a clear purpose and there is no bloat or deficiency for the apparent scope.
The server covers search and read operations for both Drive and Gmail, but lacks any write or update capabilities (e.g., create, delete, send). This is a notable gap that may require additional tools for full lifecycle coverage.