Skip to content
NewsProduct launch

Cursor ships Google Workspace plugins giving agents read-write access to Gmail, Drive, Docs, Sheets, and Calendar

· by Pondero Newsdesk

The short version

Five Cursor plugins released August 3, 2026 give coding agents direct control over Gmail, Google Drive, Google Docs, Google Sheets, and Google Calendar without leaving the editor.

Cursor ships Google Workspace plugins giving agents read-write access to Gmail, Drive, Docs, Sheets, and Calendar

Five Cursor plugins released August 3, 2026 let a coding agent pull a spec from Google Drive, flag the relevant Gmail thread, update a Sheet with test results, and book a Calendar standup, all without leaving the editor. The update, detailed in Cursor's changelog, extends the editor's agent capabilities beyond the codebase into live productivity software for the first time.

If you want to try these workflows on your own projects, Cursor is available here.

What the five plugins do

Each plugin maps to one Google Workspace app and exposes a distinct set of agent actions, per the August 3 changelog:

Gmail: Agents can search and read mail, draft and send messages, apply labels, and manage threads. The draft-and-send capability means an agent can generate a status update for a client or a pull request summary for a teammate without the developer composing the message manually.

Google Drive: Agents can search files and folders, open and download content, and create and organize files. Pulling a product spec or requirements document from Drive before generating code is one of the most common context-gathering steps in a coding session; the plugin makes it agent-callable.

Google Docs: Agents can open and read documents, write and edit text, and create new Docs. The write-and-edit capability runs in both directions: not just reading context from Docs but pushing summaries, draft PRDs, or meeting notes back in.

Google Sheets: Agents can read ranges and find values, update cells, and create and edit spreadsheets. For teams that track feature flags, bug counts, or experiment results in Sheets, an agent can now update those rows as part of the same task loop that writes the code change.

Google Calendar: Agents can read schedules, create and update events, and find free time. Checking for a scheduling conflict, booking a standup, or updating a sprint ceremony all become agent-callable operations.

The five plugins are available through the Cursor Marketplace or directly from the Customize page inside Cursor, per the changelog.

What this changes about the editor-to-workflow gap

Before these plugins, Cursor agents operated almost entirely within the file system and codebase. They could read source files, propose edits, run terminal commands, and search the web. What they could not do was read the Gmail thread describing the bug, update the Sheet tracking sprint velocity, or check whether the on-call engineer had a meeting conflict before scheduling a hotfix call.

That boundary forced developers to switch tools: open a browser tab, read the spec, copy the key details into the chat, then return to Cursor. The new plugins collapse that step. An agent now has direct API access to the same Workspace objects the developer would otherwise open manually.

The scope of what this unlocks is wider than a single app. A developer debugging a production incident might ask an agent to: read the incident thread in Gmail, find the relevant runbook in Drive, check the on-call engineer's Calendar for availability, and draft a post-mortem outline in Docs. That four-step workflow previously required four separate browser tabs. It can now run inside one Cursor session.

For teams with managed Google Workspace accounts, the change raises a configuration question that the changelog did not address. Gmail send and Calendar event-creation modify objects in another person's mailbox or calendar and are typically governed by Google Workspace API scopes and domain administrator policy. Teams using Cursor in a managed Google Workspace environment should confirm with their admin whether the Cursor OAuth app requires explicit domain-level approval before enabling Gmail send or Calendar write access for their developers.

How this positions Cursor against competitors

GitHub Copilot and Windsurf do not currently offer native Google Workspace read-write integrations in their agent layers. Copilot operates within GitHub-connected surfaces and Visual Studio; Windsurf's Cascade agent mode focuses on repository context and web search. Neither publishes a plugin marketplace with Workspace capabilities as of August 4, 2026.

Cursor has moved steadily toward a broader agent model since it introduced background agents in 2025. The Workspace plugins extend that trajectory from code tasks into the surrounding workflow layer. The August 3 changelog did not specify whether these plugins surface inside Cursor Automations (the persistent, always-on agent mode) or only in interactive chat sessions. That distinction matters for teams that want unattended agents running recurring Workspace tasks, such as a nightly Sheet update or a Calendar event created automatically after a CI run.

The competitive implication for teams evaluating AI code editors: Cursor now offers a credible answer to the question of whether the AI assistant can handle the surrounding workflow, not just the code. Whether that bundled approach is preferable to connecting a standalone agent platform (such as Lindy or a custom n8n workflow) to the same Workspace APIs depends on how tightly a team's Workspace usage is coupled to its coding sessions.

What to watch next

Two open questions will shape how quickly enterprise teams adopt the Google Workspace plugins. The first is OAuth scope approval. If Cursor's Workspace OAuth app requires Google admin consent at the domain level, larger organizations will face an IT review cycle before developers can enable Gmail send or Calendar write. Individual developers on personal or unmanaged accounts can enable the plugins now through the Marketplace.

The second is whether Cursor Automations gains access to the Workspace plugins. Background agents that monitor Gmail for specific threads, update a Sheet on a schedule, or create Calendar events without a developer actively in the session would represent a qualitatively different tier of capability. An agent that acts persistently across the Workspace, rather than on demand within a single chat, is a different product than what Cursor shipped on August 3.

Ready to connect your Cursor agents to Google Workspace? Get started with Cursor here.

Sources