🛠️ Google Drive tool MCP server 💪 all 17 operations

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? [Join the community](https://www.skool.com/beyond nodes automation lab 2006/a...

Best for

File Management automation workflows
AI Chatbot automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.mcptrigger, n8n-nodes-base.googledrivetool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Ashby.

Original n8n.io source

1.1 Workflow description

Title: 🛠️ Google Drive tool MCP server 💪 all 17 operations
Workflow name: 🛠️ Google Drive tool MCP server 💪 all 17 operations

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?

Join the community

Complete MCP server exposing all Google Drive Tool operations to AI agents. Zero configuration needed - all 17 operations pre-built.

⚡ Quick Setup

Import this workflow into your n8n instance
Activate the workflow to start your MCP server
Copy the webhook URL from the MCP trigger node
Connect AI agents using the MCP URL

🔧 How it Works

• MCP Trigger: Serves as your server endpoint for AI agent requests • Tool Nodes: Pre-configured for every Google Drive Tool operation • AI Expressions: Automatically populate parameters via $fromAI() placeholders • Native Integration: Uses official n8n Google Drive Tool tool with full error handling

📋 Available Operations (17 total)

Every possible Google Drive Tool operation is included:

📄 File (8 operations)

• Copy file • Create file from text • Delete a file • Download file • Move file • Share file • Update file • Upload file

🔧 Filefolder (1 operations)

• Search files and folders

📁 Folder (3 operations)

• Create folder • Delete folder • Share folder

🔧 Drive (5 operations)

• Create shared drive • Delete shared drive • Get shared drive • Get many shared drives • Update shared drive

🤖 AI Integration

Parameter Handling: AI agents automatically provide values for: • Resource IDs and identifiers • Search queries and filters • Content and data payloads • Configuration options

Response Format: Native Google Drive Tool API responses with full data structure

Error Handling: Built-in n8n error management and retry logic

💡 Usage Examples

Connect this MCP server to any AI agent or workflow:

• Claude Desktop: Add MCP server URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • Other n8n Workflows: Call MCP tools from any workflow • API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

• Complete Coverage: Every Google Drive Tool operation available • Zero Setup: No parameter mapping or configuration needed • AI-Ready: Built-in $fromAI() expressions for all parameters • Production Ready: Native n8n error handling and logging • Extensible: Easily modify or add custom logic

> 🆓 Free for community use! Ready to deploy in under 2 minutes.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Workflow Overview 0

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Google Drive Tool MCP Server

Type / Role: @n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices: Version 1

Block 3 - Copy file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 4 - Create file from text

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 5 - Delete a file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 6 - Download file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 7 - Move file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 8 - Share file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 9 - Update file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 10 - Upload file

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 11 - Sticky Note 1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 12 - Search files and folders

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 13 - Sticky Note 2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 14 - Create folder

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 15 - Delete folder

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 16 - Share folder

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 17 - Sticky Note 3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 18 - Create shared drive

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 19 - Delete shared drive

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 20 - Get shared drive

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 21 - Get many shared drives

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 22 - Update shared drive

Type / Role: n8n-nodes-base.googleDriveTool - googleDriveTool
Config choices: Version 3

Block 23 - Sticky Note 4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	🛠️ Google Drive tool MCP server 💪 all 17 operations
Complexity	advanced
Nodes	23
Categories	File Management, AI Chatbot
Author	David Ashby
Published	24 Jun 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/5254/5254.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source File Management workflows AI Chatbot workflows

Frequently asked questions

What does 🛠️ Google Drive tool MCP server 💪 all 17 operations do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management, AI Chatbot use case.

David Ashby

204 workflows

Nodes

n8n-nodes-base.stickynote @n8n/n8n-nodes-langchain.mcptrigger n8n-nodes-base.googledrivetool

Complexity

advanced

Published 24 Jun 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/5254/5254.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Export WordPress data to a CSV file

## Quick Overview This workflow manually exports all records from a WordPress site, converts the returned JSON into a CSV file, and saves the CSV to disk on the n8n server. ## How it works 1. Starts when you manually click Execute in n8n. 2. Fetches all available items from your connected WordPress site via the WordPress API. 3. Converts the WordPress JSON response into a CSV file. 4. Writes the generated CSV to the n8n server as `data.csv`. ## Setup 1. Add WordPress API credentials in n8n (site URL, username, and an Application Password). 2. Choose the WordPress resource to export in the WordPress node and confirm the data shape matches what you want in the CSV. 3. Update the output file path/name in the file-writing step and ensure the target directory is writable on your n8n host (for example `/home/node/.n8n/data.csv`).

View

Aggregate shipment tracking statuses with FedEx, UPS and DHL

## Quick Overview This workflow runs every 15 minutes to fetch active shipments from an n8n Data Table, query FedEx, UPS, or DHL tracking APIs with circuit-breaker protection, normalize each response into a shared status schema, and upsert the latest status back into the same table. ## How it works 1. Runs every 15 minutes on a schedule. 2. Loads all rows from the n8n Data Table `shipment_tracking` and filters out shipments already marked as DELIVERED or RETURNED_TO_SENDER. 3. Routes each remaining shipment by `carrier` and marks unsupported carriers with a canonicalStatus of UNKNOWN. 4. For FedEx, UPS, and DHL shipments, checks a per-carrier circuit breaker and either calls the carrier’s tracking API or skips the call when the breaker is open. 5. Normalizes each carrier response (or skip) into a canonical status (for example PRE_TRANSIT, IN_TRANSIT, OUT_FOR_DELIVERY, DELIVERED, EXCEPTION, UNKNOWN) while updating the breaker state based on 429/5xx/network failures. 6. Merges all carrier results and upserts the latest fields back into the `shipment_tracking` Data Table using `trackingNumber` as the match key. ## Setup 1. Create the n8n Data Table named `shipment_tracking` with columns such as `trackingNumber`, `carrier`, `canonicalStatus`, `rawStatus`, `breakerState`, `httpStatus`, and `checkedAt`, and seed it with shipments (use lowercase carriers: `fedex`, `ups`, `dhl`). 2. Add OAuth2 credentials for the FedEx Track API and select them in the FedEx HTTP request step. 3. Add OAuth2 credentials for the UPS Track API and select them in the UPS HTTP request step. 4. Add DHL API authentication (as configured for the DHL request in this template) and select it in the DHL HTTP request step. 5. Activate the workflow so workflow static data persists between runs and the circuit breaker state is maintained.

View

Clean up watched Jellyfin media and completed torrents with Transmission

## Quick Overview This scheduled workflow cleans up watched media in Jellyfin and removes completed torrents from Transmission by calling both APIs, deleting played items in Jellyfin, refreshing the Jellyfin library, and deleting torrents (including local data) once they reach the completed status. ## How it works 1. Runs daily on a schedule at the configured hour. 2. Sets the Jellyfin base URL, Jellyfin user ID, and Transmission base URL used for subsequent API calls. 3. Fetches played Movies and Episodes from Jellyfin for the configured user, deletes each returned item, and triggers a Jellyfin library refresh. 4. Calls the Transmission RPC endpoint to retrieve the required X-Transmission-Session-Id, then re-requests the torrent list using that session header. 5. Splits the Transmission response into individual torrents, filters to those with status 6 (completed), and removes each matching torrent while also deleting its local data. ## Setup 1. Add Jellyfin HTTP Header Auth credentials (for example, an API key header) and fill in the Jellyfin server URL and target Jellyfin user ID in the Variables step. 2. Add Transmission Bearer Auth credentials and set your Transmission base URL in the Variables step. 3. Confirm your Transmission instance allows RPC access at `/transmission/rpc` and that your Jellyfin server exposes the `/Users/{userId}/Items`, `/Items/{id}`, and `/Library/Refresh` endpoints for the provided credentials.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

🛠️ Google Drive tool MCP server 💪 all 17 operations

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

⚡ Quick Setup

🔧 How it Works

📋 Available Operations (17 total)

📄 File (8 operations)

🔧 Filefolder (1 operations)

📁 Folder (3 operations)

🔧 Drive (5 operations)

🤖 AI Integration

💡 Usage Examples

✨ Benefits

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Workflow Overview 0

Block 2 - Google Drive Tool MCP Server

Block 3 - Copy file

Block 4 - Create file from text

Block 5 - Delete a file

Block 6 - Download file

Block 7 - Move file

Block 8 - Share file

Block 9 - Update file

Block 10 - Upload file

Block 11 - Sticky Note 1

Block 12 - Search files and folders

Block 13 - Sticky Note 2

Block 14 - Create folder

Block 15 - Delete folder

Block 16 - Share folder

Block 17 - Sticky Note 3

Block 18 - Create shared drive

Block 19 - Delete shared drive

Block 20 - Get shared drive

Block 21 - Get many shared drives

Block 22 - Update shared drive

Block 23 - Sticky Note 4

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions