google-drive-rag-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TARGET_FOLDER_IDS | Yes | Comma-separated list of Google Drive folder IDs to scope access to. | |
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Path to the Google service account JSON key file. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesA | List files in the target Google Drive folders. Use this to discover files before reading them. Returns a JSON array of objects with 'id', 'name', and 'mimeType'. Pass the 'id' to read_file to retrieve file contents. |
| list_foldersA | List subfolders within the target Google Drive folders. Use this before list_files when you need to scope a search to a specific subfolder. Returns a JSON array of objects with 'id' and 'name'. Pass a folder 'id' to list_files as folder_id to narrow the search scope. |
| read_fileA | Read and return the full text content of a file in the target Google Drive folder. Typical workflow: call list_files to find the file and obtain its 'id', then pass that id here. |
| search_contentA | Search for a keyword or phrase within the content of files in the target Google Drive folders. Unlike list_files (which filters by filename), this tool searches inside file contents and returns matching files with a surrounding context snippet. Typical workflow: use this to find which files mention a topic, then call read_file on specific files for the full content. |
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 4 tools
Each tool has a distinct, non-overlapping purpose: listing files vs. folders vs. reading content vs. searching within content. Descriptions clarify when to use each.
All tool names follow a consistent verb_noun snake_case pattern (list_files, list_folders, read_file, search_content), making them predictable.
With 4 tools, the set is well-scoped for a RAG server focused on a specific Google Drive folder. Each tool serves a necessary function without redundancy.
The tool set covers the full workflow for content retrieval: navigate folders, list files, read content, and search within content. No obvious gaps for the intended use case.