Apps Script MCP
This server provides AI agents with secure access to Google Workspace APIs through 50 curated tools, without requiring a GCP project, OAuth consent screen, or client secrets setup.
Key Features
Simplified auth via Google's
claspCLI — no GCP setup neededAI agents never handle credentials directly (security boundary enforced)
Multi-user support via
user_google_emailparameter for credential isolationEvery tool call is logged for audit purposes
Gmail — Search messages, retrieve by ID, send emails (plain/HTML, CC/BCC), list labels, modify labels (archive, star, trash, etc.)
Google Drive — Search files/folders, list folder contents, get file content, create/delete/trash files and folders, share files, and manage permissions
Google Sheets — List spreadsheets, read/write/append cell values, create new spreadsheets, get metadata (sheet names, properties)
Google Calendar — List calendars, get/create/update/delete events (including all-day events with attendees)
Google Docs — Search documents, get content, create new docs, modify text (insert or find-and-replace), append text
Apps Script (17 tools) — Full lifecycle management:
List, get, create, update, and delete script projects
Execute functions in deployed scripts
Manage deployments (create, list, update, delete) and versions (create, list, get)
Monitor execution processes and retrieve daily/weekly metrics
Generate trigger code for time-based and event-driven triggers (on-edit, on-open, on-form-submit, etc.)
Authentication — Start and complete the Google OAuth flow directly via MCP tools
Uses Google OAuth authentication to provide secure access to Apps Script projects and related development tools.
Provides tools to create, manage, edit, and execute Apps Script projects, including script deployment and execution monitoring.
Integrates with Google Cloud projects to manage API permissions and OAuth credentials required for script execution and deployment.
Interacts with the Google Drive API to list and manage script projects stored within the user's account.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Apps Script MCP list my script projects and show me the files in 'Email Automation'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Automation MCP
Google Workspace APIs for AI agents - no GCP project required.
Uses clasp for authentication. No GCP console, no OAuth consent screen, no client secrets. Just authenticate and go.
Quick Start
uvx google-automation-mcp auth # 1. Browser sign-in via clasp
uvx google-automation-mcp # 4. Run serverFirst run walks you through three one-time steps:
gmcp auth- opens browser for Google sign-in (clasp OAuth)Enable Apps Script API -
gmcp authchecks and prompts you to toggle ON at https://script.google.com/home/usersettings (5 seconds)Authorize scopes -
gmcp authdeploys a Web App router and prints a URL. Open it, click "Allow" to grant Gmail/Drive/Sheets/Calendar/Docs/Forms/Tasks accessDone - run
gmcporuvx google-automation-mcpto start the server
Check status anytime: gmcp status
Tip: Use the short alias
gmcpafter installing.
Re-authorization: If a future update adds new scopes, revoke the app at myaccount.google.com/permissions (find "MCP-Router"), then visit the Web App URL again from
gmcp status.
Related MCP server: Clasp Enhanced MCP Server
Clasp Router vs REST API
Workspace tools (Gmail, Drive, Sheets, etc.) can operate in two modes. The clasp router is the default and requires no GCP project. Traditional Google API setup requires creating a GCP project, enabling APIs, configuring an OAuth consent screen, adding test users, and creating credentials.
Clasp Router (default) | REST API (with OAuth 2.1) | |
Setup time | ~2 min (browser sign-in + one toggle + one Allow click) | ~15 min (GCP project + enable APIs + OAuth consent screen + credentials) |
GCP project | Not needed | Required |
How it works | Deploys an Apps Script Web App per user; tool calls routed via HTTP POST | Calls Google REST APIs directly with OAuth tokens |
Latency | ~1-3s per call (Apps Script execution overhead) | ~100-300ms per call |
Execution timeout | 30s per call (Apps Script limit) | No per-call limit |
Best for | Personal use, prototyping, AI agents | High-volume, production, low-latency apps |
Daily quotas (free consumer Google account)
Service | Clasp Router (Apps Script limits) | REST API limits |
Gmail send | 100 recipients/day | 500 emails/day (Gmail API) |
Gmail read | 50,000 reads/day | 250 quota units/s per user |
Drive | 90 min total runtime/day | 1 billion API calls/day (project) |
Sheets | 90 min total runtime/day | 300 requests/min per project |
Calendar | 5,000 events created/day | 1M queries/day per project |
Docs | 90 min total runtime/day | 300 requests/min per project |
Forms | 90 min total runtime/day | No published limit |
Tasks | Same as REST (calls Tasks API via | 50,000 requests/day |
Note: Apps Script runtime limits are shared across all services. The 90 min/day limit applies to total execution time, not per-service. At ~2s per call, that's ~2,700 tool calls/day. Full Apps Script quotas
Backend selection
The backend is selected automatically: if GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET are set, REST APIs are used. Otherwise, the clasp router handles Workspace calls.
Override with MCP_USE_ROUTER=true or MCP_USE_ROUTER=false to force a specific backend.
For multi-user production deployments requiring your own OAuth credentials:
export GOOGLE_OAUTH_CLIENT_ID='...'
export GOOGLE_OAUTH_CLIENT_SECRET='...'
gmcp auth --oauth21Security: AI Never Sees Credentials
Direct API | This MCP | |
Credentials | AI handles tokens directly | AI never sees tokens |
API access | Any endpoint | 60 curated tools only |
Audit | Build your own | Every tool call logged |
The MCP acts as a security boundary. Your AI agent calls tools; the MCP handles authentication internally.
MCP Client Configuration
Claude Desktop (One-Click Install):
Download google-automation-mcp.dxt and open it. Claude Desktop will install automatically.
Claude Code (~/.mcp.json):
{
"mcpServers": {
"google": {
"type": "stdio",
"command": "uvx",
"args": ["google-automation-mcp"]
}
}
}Claude Desktop (Manual) (claude_desktop_config.json):
{
"mcpServers": {
"google": {
"command": "uvx",
"args": ["google-automation-mcp"]
}
}
}Gemini CLI:
gemini extensions install github:sam-ent/google-automation-mcpAvailable Tools (60)
Gmail (5)
search_gmail_messages · get_gmail_message · send_gmail_message · list_gmail_labels · modify_gmail_labels
Drive (10)
search_drive_files · list_drive_items · get_drive_file_content · create_drive_file · create_drive_folder · delete_drive_file · trash_drive_file · share_drive_file · list_drive_permissions · remove_drive_permission
Sheets (6)
list_spreadsheets · get_sheet_values · update_sheet_values · append_sheet_values · create_spreadsheet · get_spreadsheet_metadata
Calendar (5)
list_calendars · get_events · create_event · update_event · delete_event
Docs (5)
get_doc_content · search_docs · create_doc · modify_doc_text · append_doc_text
Forms (4)
get_form · create_form · add_form_question · get_form_responses
Tasks (6)
list_task_lists · get_tasks · create_task · update_task · delete_task · complete_task
Apps Script (17)
list_script_projects · get_script_project · get_script_content · create_script_project · update_script_content · delete_script_project · run_script_function · create_deployment · list_deployments · update_deployment · delete_deployment · list_versions · create_version · get_version · list_script_processes · get_script_metrics · generate_trigger_code
Auth (2)
start_google_auth · complete_google_auth
Multi-User Support
All tools accept user_google_email for per-user credential isolation:
search_gmail_messages(user_google_email="alice@example.com", query="is:unread")
search_gmail_messages(user_google_email="bob@example.com", query="is:unread")Credentials stored separately: ~/.secrets/google-automation-mcp/credentials/{email}.json
Apps Script: Extending Google Workspace
Apps Script tools let you deploy code that runs inside Google apps - things REST APIs cannot do:
Capability | Example |
Custom spreadsheet functions |
|
Real-time triggers |
|
Custom menus | Add menu items to Sheets/Docs |
Webhooks |
|
# Create a bound script with custom function
create_script_project(title="Validator", parent_id="SPREADSHEET_ID")
update_script_content(script_id="...", files=[{
"name": "Code",
"type": "SERVER_JS",
"source": "function VALIDATE_EMAIL(e) { return /^[^@]+@[^@]+\\.[^@]+$/.test(e); }"
}])Limitations
run_script_function requires one-time setup per script: Open script at script.google.com -> Project Settings -> Change GCP project -> Deploy as API Executable. Once configured, functions can be called repeatedly. All other tools work without this setup.
CLI Reference
Short alias: gmcp (or full name: google-automation-mcp)
gmcp # Run server
gmcp setup # Interactive setup wizard
gmcp auth # Authenticate with clasp
gmcp auth --oauth21 # OAuth 2.1 for production
gmcp status # Check auth status
gmcp version # Show versionDevelopment
git clone https://github.com/sam-ent/google-automation-mcp.git
cd google-automation-mcp
uv sync
uv run pytest tests/ -v # 183 testsAcknowledgments
Built on google_workspace_mcp by Taylor Wilsdon (MIT License).
License
MIT
Available Tools
50 toolsappend_doc_text_toolA
Append text to the end of a Google Doc.
Args: user_google_email: The user's Google email address document_id: The document ID text: Text to append to the end of the document
Inputs: user_google_email (required), document_id (required), text (required). Returns: result
append_sheet_values_toolA
Append values to a Google Sheet (adds rows after existing data).
Args: user_google_email: The user's Google email address spreadsheet_id: The spreadsheet ID range: A1 notation range to append to (e.g., "Sheet1!A:D" or "Sheet1") values: 2D array of values to append. Example: [["Value1", "Value2"], ["Value3", "Value4"]] value_input: How input values should be interpreted - "USER_ENTERED" or "RAW"
Inputs: user_google_email (required), spreadsheet_id (required), range (required), values (required), +1 more. Returns: result
complete_google_auth_toolA
Complete the Google OAuth flow with the redirect URL.
Args: redirect_url: The full URL from the browser after authorization (looks like: http://localhost/?code=4/0A...&scope=...)
Inputs: redirect_url (required). Returns: result
create_deployment_toolB
Create a new deployment of the script.
Args: script_id: The script project ID description: Deployment description version_description: Optional version description (defaults to deployment description)
Inputs: script_id (required), description (required), version_description. Returns: result
create_doc_toolC
Create a new Google Doc.
Args: user_google_email: The user's Google email address title: Document title content: Optional initial content
Inputs: user_google_email (required), title (required), content. Returns: result
create_drive_file_toolB
Create a new file in Google Drive.
Args: user_google_email: The user's Google email address file_name: Name for the new file content: File content (text) folder_id: Parent folder ID (default: 'root') mime_type: MIME type of the file (default: 'text/plain')
Inputs: user_google_email (required), file_name (required), content, folder_id, +1 more. Returns: result
create_drive_folder_toolA
Create a new folder in Google Drive.
Args: user_google_email: The user's Google email address folder_name: Name for the new folder parent_id: Parent folder ID (default: 'root' for My Drive root)
Inputs: user_google_email (required), folder_name (required), parent_id. Returns: result
create_event_toolA
Create a new calendar event.
Args: user_google_email: The user's Google email address summary: Event title start_time: Start time in ISO format (e.g., "2024-01-15T09:00:00") or date for all-day (e.g., "2024-01-15") end_time: End time in ISO format (e.g., "2024-01-15T10:00:00") or date for all-day (e.g., "2024-01-16") calendar_id: Calendar ID (default: 'primary') description: Optional event description location: Optional event location attendees: Optional comma-separated list of attendee emails all_day: If True, create an all-day event (use date format for start/end)
Inputs: user_google_email (required), summary (required), start_time (required), end_time (required), +5 more. Returns: result
create_script_project_toolA
Create a new Apps Script project (standalone or bound to a document).
Args: title: Project title parent_id: Optional - the Google Drive ID of a container document to bind to. Leave empty for standalone scripts.
To create a BOUND script, pass the ID of:
- Google Sheet (from the URL: docs.google.com/spreadsheets/d/{ID}/edit)
- Google Doc (from the URL: docs.google.com/document/d/{ID}/edit)
- Google Form (from the URL: docs.google.com/forms/d/{ID}/edit)
- Google Slides (from the URL: docs.google.com/presentation/d/{ID}/edit)
Bound scripts can use document-specific features like custom menus,
onOpen triggers, and getActiveSpreadsheet().Inputs: title (required), parent_id. Returns: result
create_spreadsheet_toolB
Create a new Google Spreadsheet.
Args: user_google_email: The user's Google email address title: Title for the new spreadsheet sheet_names: Optional list of sheet names to create (default: ["Sheet1"])
Inputs: user_google_email (required), title (required), sheet_names. Returns: result
create_version_toolA
Create a new immutable version of a script project.
Versions capture a snapshot of the current script code. Once created, versions cannot be modified.
Args: script_id: The script project ID description: Optional description for this version
Inputs: script_id (required), description. Returns: result
delete_deployment_toolC
Delete a deployment.
Args: script_id: The script project ID deployment_id: The deployment ID to delete
Inputs: script_id (required), deployment_id (required). Returns: result
delete_drive_file_toolA
Permanently delete a file from Google Drive.
WARNING: This permanently deletes the file. Use trash_drive_file for recoverable deletion.
Args: user_google_email: The user's Google email address file_id: The file ID to delete
Inputs: user_google_email (required), file_id (required). Returns: result
delete_event_toolA
Delete a calendar event.
Args: user_google_email: The user's Google email address event_id: The event ID to delete calendar_id: Calendar ID (default: 'primary')
Inputs: user_google_email (required), event_id (required), calendar_id. Returns: result
delete_script_project_toolA
Delete an Apps Script project.
WARNING: This permanently deletes the script project. The action cannot be undone.
Args: script_id: The script project ID to delete
Inputs: script_id (required). Returns: result
generate_trigger_codeA
Generate Apps Script code for creating triggers.
The Apps Script API cannot create triggers directly - they must be created from within Apps Script itself. This tool generates the code you need.
Args: trigger_type: Type of trigger. One of: - "time_minutes" (run every N minutes: 1, 5, 10, 15, 30) - "time_hours" (run every N hours: 1, 2, 4, 6, 8, 12) - "time_daily" (run daily at a specific hour: 0-23) - "time_weekly" (run weekly on a specific day) - "on_open" (simple trigger - runs when document opens) - "on_edit" (simple trigger - runs when user edits) - "on_form_submit" (runs when form is submitted) - "on_change" (runs when content changes)
function_name: The function to run when trigger fires (e.g., "sendDailyReport")
schedule: Schedule details (depends on trigger_type):
- For time_minutes: "1", "5", "10", "15", or "30"
- For time_hours: "1", "2", "4", "6", "8", or "12"
- For time_daily: hour as "0"-"23" (e.g., "9" for 9am)
- For time_weekly: "MONDAY", "TUESDAY", etc.
- For simple triggers (on_open, on_edit): not neededReturns: Apps Script code to create the trigger. User should add this to their script and run the setup function once to install the trigger.
Inputs: trigger_type (required), function_name (required), schedule. Returns: result
get_doc_content_toolC
Get the content of a Google Doc.
Args: user_google_email: The user's Google email address document_id: The document ID
Inputs: user_google_email (required), document_id (required). Returns: result
get_drive_file_content_toolA
Get the content of a Google Drive file.
Supports Google Docs (-> text), Sheets (-> CSV), Slides (-> text), and text files.
Args: user_google_email: The user's Google email address file_id: The Drive file ID
Inputs: user_google_email (required), file_id (required). Returns: result
get_events_toolB
Get events from a calendar.
Args: user_google_email: The user's Google email address calendar_id: Calendar ID (default: 'primary') max_results: Maximum number of events to return (default: 10) time_min: Start time in ISO format (default: now) time_max: End time in ISO format (default: 7 days from now) query: Optional search query string
Inputs: user_google_email (required), calendar_id, max_results, time_min, +2 more. Returns: result
get_gmail_message_toolB
Get a specific Gmail message by ID.
Args: user_google_email: The user's Google email address message_id: The message ID to retrieve format: Message format - "full", "metadata", or "minimal"
Inputs: user_google_email (required), message_id (required), format. Returns: result
get_script_content_toolB
Retrieve content of a specific file within a project.
Args: script_id: The script project ID file_name: Name of the file to retrieve (e.g., "Code", "appsscript")
Inputs: script_id (required), file_name (required). Returns: result
get_script_metrics_toolB
Get execution metrics for a script project.
Returns analytics data including active users, total executions, and failed executions over time.
Args: script_id: The script project ID metrics_granularity: Granularity of metrics - "DAILY" or "WEEKLY"
Inputs: script_id (required), metrics_granularity. Returns: result
get_script_project_toolC
Retrieve complete project details including all source files.
Args: script_id: The script project ID
Inputs: script_id (required). Returns: result
get_sheet_values_toolB
Get values from a Google Sheet.
Args: user_google_email: The user's Google email address spreadsheet_id: The spreadsheet ID range: A1 notation range (e.g., "Sheet1!A1:D10" or just "Sheet1") value_render: How values should be rendered - "FORMATTED_VALUE", "UNFORMATTED_VALUE", or "FORMULA"
Inputs: user_google_email (required), spreadsheet_id (required), range, value_render. Returns: result
get_spreadsheet_metadata_toolC
Get metadata about a spreadsheet including all sheet names and properties.
Args: user_google_email: The user's Google email address spreadsheet_id: The spreadsheet ID
Inputs: user_google_email (required), spreadsheet_id (required). Returns: result
get_version_toolB
Get details of a specific version.
Args: script_id: The script project ID version_number: The version number to retrieve (1, 2, 3, etc.)
Inputs: script_id (required), version_number (required). Returns: result
list_calendars_toolC
List all calendars accessible to the user.
Args: user_google_email: The user's Google email address
Inputs: user_google_email (required). Returns: result
list_deployments_toolC
List all deployments for a script project.
Args: script_id: The script project ID
Inputs: script_id (required). Returns: result
list_drive_items_toolB
List files and folders in a Drive folder.
Args: user_google_email: The user's Google email address folder_id: The folder ID to list (default: 'root' for My Drive root) page_size: Maximum number of items to return (default: 50)
Inputs: user_google_email (required), folder_id, page_size. Returns: result
list_drive_permissions_toolC
List all permissions on a file or folder.
Args: user_google_email: The user's Google email address file_id: The file or folder ID
Inputs: user_google_email (required), file_id (required). Returns: result
list_gmail_labels_toolC
List all Gmail labels for the user.
Args: user_google_email: The user's Google email address
Inputs: user_google_email (required). Returns: result
list_script_processes_toolB
List recent execution processes for user's scripts.
Args: page_size: Number of results (default: 50) script_id: Optional filter by script ID
Inputs: page_size, script_id. Returns: result
list_script_projects_toolA
List Google Apps Script projects accessible to the user.
Args: page_size: Number of results per page (default: 50) page_token: Token for pagination (optional)
Inputs: page_size, page_token. Returns: result
list_spreadsheets_toolC
List Google Sheets spreadsheets in Drive.
Args: user_google_email: The user's Google email address query: Optional search query to filter spreadsheets page_size: Maximum number of spreadsheets to return (default: 20)
Inputs: user_google_email (required), query, page_size. Returns: result
list_versions_toolA
List all versions of a script project.
Versions are immutable snapshots of your script code. They are created when you deploy or explicitly create a version.
Args: script_id: The script project ID
Inputs: script_id (required). Returns: result
modify_doc_text_toolB
Modify text in a Google Doc.
Args: user_google_email: The user's Google email address document_id: The document ID text: Text to insert (or replace with) index: Position to insert text (default: 1, start of document) replace_text: If provided, find and replace this text with 'text'
Inputs: user_google_email (required), document_id (required), text (required), index, +1 more. Returns: result
modify_gmail_labels_toolA
Modify labels on a Gmail message.
Common label IDs:
INBOX - Message in inbox
UNREAD - Message is unread
STARRED - Message is starred
TRASH - Message in trash
SPAM - Message in spam
IMPORTANT - Message marked important
Args: user_google_email: The user's Google email address message_id: The message ID to modify add_labels: List of label IDs to add (e.g., ["STARRED", "IMPORTANT"]) remove_labels: List of label IDs to remove (e.g., ["UNREAD", "INBOX"])
Examples: - Archive: remove_labels=["INBOX"] - Mark read: remove_labels=["UNREAD"] - Mark unread: add_labels=["UNREAD"] - Star: add_labels=["STARRED"] - Move to trash: add_labels=["TRASH"]
Inputs: user_google_email (required), message_id (required), add_labels, remove_labels. Returns: result
remove_drive_permission_toolB
Remove a permission from a file or folder.
Args: user_google_email: The user's Google email address file_id: The file or folder ID permission_id: The permission ID to remove (from list_drive_permissions)
Inputs: user_google_email (required), file_id (required), permission_id (required). Returns: result
run_script_function_toolA
Execute a function in a deployed script.
Note: Requires the script to be deployed as "API Executable" in the Apps Script editor. See README for setup instructions.
Args: script_id: The script project ID function_name: Name of function to execute parameters: Optional list of parameters to pass to the function dev_mode: If True, run latest code; if False, run deployed version
Inputs: script_id (required), function_name (required), parameters, dev_mode. Returns: result
search_docs_toolC
Search for Google Docs by name.
Args: user_google_email: The user's Google email address query: Search query string page_size: Maximum number of docs to return (default: 10)
Inputs: user_google_email (required), query (required), page_size. Returns: result
search_drive_files_toolA
Search for files and folders in Google Drive.
Args: user_google_email: The user's Google email address query: Search query string. Supports Drive query operators: - name contains 'example' - mimeType = 'application/vnd.google-apps.spreadsheet' - fullText contains 'keyword' - modifiedTime > '2024-01-01' page_size: Maximum number of files to return (default: 10)
Inputs: user_google_email (required), query (required), page_size. Returns: result
search_gmail_messages_toolB
Search for Gmail messages matching a query.
Args: user_google_email: The user's Google email address query: Gmail search query (e.g., "from:user@example.com subject:hello") max_results: Maximum number of messages to return (default: 10)
Inputs: user_google_email (required), query, max_results. Returns: result
send_gmail_message_toolB
Send a Gmail message.
Args: user_google_email: The user's Google email address to: Recipient email address(es), comma-separated subject: Email subject body: Email body content cc: Optional CC recipients, comma-separated bcc: Optional BCC recipients, comma-separated html: If True, body is treated as HTML
Inputs: user_google_email (required), to (required), subject (required), body (required), +3 more. Returns: result
start_google_auth_toolA
Start Google OAuth authentication flow.
Returns an authorization URL that must be opened in a browser. After authorizing, call complete_google_auth with the redirect URL.
Inputs: no named parameters. Returns: result
trash_drive_file_toolC
Move a file to trash in Google Drive (recoverable).
Args: user_google_email: The user's Google email address file_id: The file ID to trash
Inputs: user_google_email (required), file_id (required). Returns: result
update_deployment_toolC
Update an existing deployment configuration.
Args: script_id: The script project ID deployment_id: The deployment ID to update description: New description for the deployment
Inputs: script_id (required), deployment_id (required), description. Returns: result
update_event_toolB
Update an existing calendar event.
Args: user_google_email: The user's Google email address event_id: The event ID to update calendar_id: Calendar ID (default: 'primary') summary: New event title (optional) start_time: New start time in ISO format (optional) end_time: New end time in ISO format (optional) description: New description (optional) location: New location (optional) attendees: New comma-separated list of attendee emails (optional) all_day: If True and updating times, use date format
Inputs: user_google_email (required), event_id (required), calendar_id, summary, +6 more. Returns: result
update_script_content_toolB
Update or create files in a script project.
Args: script_id: The script project ID files: List of file objects, each with: - name: File name (e.g., "Code", "Utils") - type: File type ("SERVER_JS", "HTML", or "JSON") - source: File content as string
Example files parameter: [{"name": "Code", "type": "SERVER_JS", "source": "function main() { Logger.log('Hello'); }"}]
Inputs: script_id (required), files (required). Returns: result
update_sheet_values_toolB
Update values in a Google Sheet.
Args: user_google_email: The user's Google email address spreadsheet_id: The spreadsheet ID range: A1 notation range (e.g., "Sheet1!A1:D10") values: 2D array of values to write. Example: [["Header1", "Header2"], ["Value1", "Value2"]] value_input: How input values should be interpreted - "USER_ENTERED" or "RAW"
Inputs: user_google_email (required), spreadsheet_id (required), range (required), values (required), +1 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 50 tools
Most tools are clearly distinct by resource type (Docs, Sheets, Drive, Calendar, Gmail, Scripts) and action (create, get, update, delete, list, search). However, some overlap exists: append_doc_text_tool and modify_doc_text_tool both modify Docs, and append_sheet_values_tool and update_sheet_values_tool both write to Sheets, which could cause confusion without careful reading of descriptions.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_doc, get_doc_content, update_sheet_values, list_script_projects). All use snake_case with clear, descriptive verbs aligned to CRUD operations, making the set predictable and easy to navigate.
With 50 tools, the count is excessive for a single server, making it overwhelming and difficult for agents to navigate efficiently. While the scope covers multiple Google services (Docs, Sheets, Drive, Calendar, Gmail, Apps Script), the sheer volume suggests poor scoping—many tools could be consolidated or split into focused sub-servers.
The tool set provides comprehensive coverage across Google services, including full CRUD operations for Docs, Sheets, Drive files, Calendar events, and Script projects, plus search, listing, and specialized actions like authentication and trigger generation. No obvious gaps exist; agents can perform end-to-end workflows without dead ends.
Maintenance
Related MCP Connectors
Search and discover Google Apps Script libraries with AI-generated summaries
Docs, decks, forms, apps you build and deploy, automations, and AI images, video and voice.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Google Apps Script projects, including project creation, file operations, and web app deployments. It features a security-first design with encrypted property management and automated security auditing for GAS environments.1MIT
- AlicenseBqualityDmaintenanceProvides comprehensive management of Google Apps Script projects via clasp CLI, enabling AI assistants to create, clone, deploy, and run scripts with full version control and deployment management.1810MIT
- AlicenseDqualityDmaintenanceEnables AI-driven development and management of Google Apps Script projects, including autonomous system construction, real-time debugging, and spreadsheet operations through natural language.766MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to create and modify Google Apps Script projects, manage versions and deployments, run functions, and inspect execution history through natural language.18116 npmMIT