Google Drive MCP: purpose and common use cases
Google Drive MCP is indexed as an MCP integration associated with google-drive. Artifiner records https://drivemcp.googleapis.com/mcp/v1 from the source configuration and groups the integration under Productivity, MCP, and Presentations; the upstream configuration remains authoritative for authentication and connection details.
Where Google Drive MCP fits in an agent workflow
Google Drive MCP is an MCP integration for productivity workflows. For Google Drive MCP, the Model Context Protocol connection is useful when a Codex workflow needs structured access to an external service, tool or data source rather than instructions alone. This entry is relevant to google-drive, mcp, and integration. It is associated with the google-drive plugin, which is the installation context for the connection.
What to check before using Google Drive MCP
Choose this MCP connection when the task requires live tool access in the productivity domain. For Google Drive MCP, verify authentication and the published endpoint before connecting it, especially if the service can read or modify account data. The Google Drive MCP endpoint and canonical source are deliberately separated from editorial copy so configuration can be checked against the upstream record.