A
licenseA
qualityF
maintenanceThis server enables users to perform Google News searches with automatic categorization and multi-language support via SerpAPI integration.
14
1
28 npm
129
MIT
Google MCP
Related Servers
Alternatives to Google MCP
- AlicenseNot gradedqualityCmaintenanceAn MCP (Model Context Protocol) server that provides Google search capabilities and webpage content analysis tools. This server enables AI models to perform Google searches and analyze webpage content programmatically.16 npm256ISC
Related Servers
- FlicenseNot gradedqualityDmaintenanceA locally-hosted MCP server that integrates Gmail, Google Calendar, and Google Drive to provide AI-powered management of emails, events, and files. It enables tool-based interactions like sending emails, creating calendar events, and searching Drive files through clients like Cursor and Claude Desktop.-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to access and manage Google Workspace services such as Gmail, Drive, Docs, Sheets, Calendar, and Slides through the MCP protocol, with built-in OAuth 2.0 authentication and read/write tool support.-
- AlicenseNot gradedqualityCmaintenanceExposes standardized tools for AI agents to interact with Google Workspace (Gmail and Google Docs) via the MCP protocol.15 npmISC
- AlicenseAqualityBmaintenanceMCP server for Google APIs — Gmail and Calendar tools for LLM agents.62MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server for managing Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Slides) through natural language with AI assistants like Claude and Cursor.12 npm1MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes 17 Google Workspace APIs (e.g., Gmail, Drive, Calendar) as auto-generated tools for AI assistants, enabling natural language control of Google services.-
TDQS
B3.2/5.0
Scored across 32 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity, as each is scoped to a specific Google service (Calendar, Drive, Gmail, Tasks) and a specific action on a resource (e.g., create, delete, list). Overlap is minimal, such as 'google_calendar_get_event' and 'google_calendar_get_events' being clearly differentiated by singular vs. plural.
Naming Consistency5/5
Tool names follow a highly consistent verb_noun pattern throughout, with a clear structure: 'google_service_action_resource' (e.g., 'google_calendar_create_event'). All tools use snake_case uniformly, and verbs are predictable (create, delete, get, list, update, etc.), making the set easy to navigate.
Tool Count3/5
With 32 tools, the count is borderline high for a single server, as it covers multiple Google services (Calendar, Drive, Gmail, Tasks). While each service is well-scoped individually, the overall set feels heavy and might be better split into separate servers, but it's not extreme (e.g., not 50+ tools).
Completeness5/5
The tool surface provides complete CRUD/lifecycle coverage for each Google service domain, with no obvious gaps. For example, Calendar has create, get, list, update, delete, plus utilities like find_free_time; Gmail includes send, draft, get, list, delete, and label management; ensuring agents can handle full workflows without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues