Connect AI agents to Google Workspace — Gmail, Drive, Calendar, Sheets, and more through MCP server integrations.
Of the 10 mcp tools for google services here, the best one to start with is google_workspace_mcp (rated SAFE by our security scan, ★ 3.3k). Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace MCP Server
MCP Tools for Google Services are AI-powered software designed to help developers and teams tackle mcp tools for google services-related tasks more efficiently. These tools are typically published as open-source projects on GitHub and can be integrated into existing workflows via MCP (Model Context Protocol), Claude Skills, or standalone agent frameworks. On Agent Skills Hub, we index 10 quality-scored MCP Tools for Google Services across languages including Python, TypeScript, Go.
In 2026, the AI agent ecosystem is maturing rapidly. MCP Tools for Google Services can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — google_workspace_mcp, backlot, modular-context-obsidian-plugin — have earned an average of 573 GitHub stars, reflecting strong community validation. 9 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing among MCP Tools for Google Services, consider these factors: 1) Community activity — GitHub stars and recent commit frequency indicate reliability; 2) Integration method — check if it supports MCP, Claude, or your preferred agent framework; 3) Language compatibility — the most common language in this list is Python; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with google_workspace_mcp — it ranks highest in both star count and quality score.
Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace MCP Server & CLI Tool
A local emulator for enterprise SaaS APIs — Slack, Gmail, Google Drive, GitHub, Jira, Notion, S3 and more — with the real response shapes, pagination, auth and per-document ACLs, over a corpus you supply.
Modular Context | Karpathy LLM Knowledge Base + Gmail & G-Cal — multi-account MCP server for Claude Code, encrypted local-first
This MCP server integrates with your Google Drive and Google Sheets, to enable creating and modifying spreadsheets.
Model Context Protocol (MCP) Server for reading from Google Drive and editing Google Sheets
A Model Context Protocol (MCP) server that provides authenticated access to Google Workspace APIs, offering integrated Authentication, Gmail, Calendar, and Drive functionality
Self-hosted AI workspace with agents, skills, and tools (Gmail, Calendar) that runs entirely on your own provider API keys (BYOK). Bring your own keys — Groq, OpenRouter, NVIDIA, Hugging Face, Google AI.
High-performance Google Drive CLI and Model Context Protocol (MCP) Server for LLM/AI agents. Natively execute Google Apps Script (GAS) under a secure whitelisted runtime sandbox, automate transfers, and manage Drive infrastructure.
Self-hosted RAG platform for AI document search across GitHub, Notion, Google Drive, local files, and web sources with citations.
Turn Google Drive PDFs into Obsidian wiki notes via NotebookLM MCP without loading full PDFs into Claude context
| Tool | Stars | Score |
|---|---|---|
| google_workspace_mcp | ★ 3.3k | 76 |
| backlot | ★ 386 | 65 |
| modular-context-obsidian-plugin | ★ 97 | 60 |
| mcp-google-sheets | ★ 1.0k | 71 |
| mcp-gdrive | ★ 283 | 41 |
| google-workspace-mcp | ★ 189 | 69 |
| ENZO | ★ 111 | 60 |
| ggsrun | ★ 171 | 70 |
| OpenDocuments | ★ 103 | 63 |
| notebooklm-wiki-pipeline | ★ 90 | 51 |
The top mcp tools for google services in 2026 are google_workspace_mcp, backlot, modular-context-obsidian-plugin. Agent Skills Hub ranks 10 options by GitHub stars, quality score (6 dimensions including completeness, examples, and agent readiness), and recent activity. The list is rebuilt every 8 hours from live GitHub data.
google_workspace_mcp (3.3k stars) is the most adopted choice for general mcp tools for google services workflows, written in Python. backlot (386 stars) is a strong alternative. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with google_workspace_mcp — it has the deepest community and the most examples online.
Avoid pre-built mcp tools for google services when (1) your use case requires deep customization that the tool's plugin system doesn't support, (2) you have strict compliance requirements that ban third-party dependencies, (3) the tool's maintenance is inactive (last commit >6 months ago), or (4) your data volume is small enough that a 50-line custom script is cheaper than learning the tool. For most production workflows above 100 requests/day, the time savings from a maintained tool outweigh the customization loss.
MCP Tools for Google Services focuses specifically on connect ai agents to google workspace — gmail, drive, calendar, sheets, and more through mcp server integrations. MCP API Integration is a related but distinct category — see https://agentskillshub.top/best/mcp-api/ for those tools. The two often appear in the same agent pipeline but solve different problems: choose mcp tools for google services when your primary goal is the specific task, and mcp api integration when the workflow is broader.
For most teams, yes. google_workspace_mcp has 3.3k stars worth of community testing, handles edge cases you haven't thought of, and ships with documentation. Build your own only when (1) your requirements are deeply non-standard, (2) you have a security/compliance reason to avoid OSS dependencies, or (3) the maintenance burden is small enough (<200 lines of code) that you'll save time long-term. The break-even point is usually around 2-3 weeks of dev time saved.
Most mcp tools for google services listed are open source under permissive licenses (MIT, Apache 2.0). A handful offer paid managed/cloud versions on top of free self-hosted core. Always check the LICENSE file on each tool's GitHub repository before commercial use — some use AGPL or non-commercial restrictions that may not fit your deployment model.
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible:
