Cursor Agents Can Now Act Across Google Workspace

Cursor is adding Google Workspace plugins that let its coding agents read, write, and act across Gmail, Google Drive, and Google Calendar. The company announced the update through its X account and says the plugins give agents direct access to those Workspace apps. (Cursor on X)

Cursor’s durable changelog says the plugins are available to browse in the Cursor Marketplace and can be installed from the Customize page. (Cursor’s Google Workspace plugins changelog)

What each plugin can do

The official changelog entry describes three plugins, and lists these capabilities:

(Cursor’s Google Workspace plugins changelog)

Cursor's Marketplace listing for the Drive plugin adds one detail the changelog leaves out: the connection runs "via Google's remote MCP server", and the plugin is published and verified by Cursor. (Cursor Marketplace: Google Drive)

The workflow shift

The update moves Cursor agents beyond repository-local work. An agent can pull context from a Drive folder, look up an email thread, or check a calendar without requiring the user to manually copy that context into the coding workspace. Cursor describes the plugins as a way to pull context, draft and update files, and manage inbox and calendar work without leaving Cursor. (Cursor’s Google Workspace plugins changelog)

That makes the integration relevant to tasks that cross engineering and operations. For example, a user could ask an agent to inspect a project brief in Drive, compare it with an implementation, then file the result back to Drive after the code work is complete. The changelog lists the underlying app actions, but it does not promise that every multi-step workflow will work without review.

How to get started

Cursor says to browse the plugins in the Cursor Marketplace and install them from the Customize page. The linked changelog does not state specific plan requirements, OAuth scopes, approval prompts, regional limits, or other permission details, so teams should confirm those details during setup rather than assuming the plugins have unrestricted access. (Cursor’s Google Workspace plugins changelog)

If you are testing the integration, start with a reversible workflow:

1. Connect only the Workspace app needed for the task.
2. Ask the agent to read and summarize before asking it to send, edit, or delete anything.
3. Use a test file, label, or calendar for the first write action.
4. Review the resulting changes in the Google app before expanding the workflow.

Why it matters for agent builders

Cursor’s earlier SDK work showed how its coding agents could be embedded in another product. These Workspace plugins take the complementary route: they bring external business context and actions into the Cursor agent surface. (Cursor’s Notion SDK case study)

The important change is not simply another connector list. Gmail, Drive, and Calendar represent the places where requirements, decisions, schedules, and operational records already live. Giving an agent direct access can reduce context switching, but it also makes permission boundaries and human review part of the workflow design.

Bottom line

Cursor’s new Google Workspace plugins let coding agents work across Gmail, Google Drive, and Google Calendar. The official changelog documents concrete read, write, and management actions and points users to the Marketplace and Customize page for installation. It does not document plan, permission, or rollout details beyond that, so treat the first connected workflow as a controlled test.

Correction (August 9, 2026)

This article originally described five plugins, adding Google Docs and Google Sheets rows with capability lists, and attributed all five to Cursor's changelog. That attribution was wrong: the August 3, 2026 changelog entry describes three plugins -- Google Drive, Gmail, and Google Calendar. The two extra rows and every mention of Docs and Sheets have been removed rather than re-sourced, because no Cursor-owned page fetched during this re-verification supports them. This correction makes no claim either way about whether separate Google Docs or Google Sheets plugins exist in the Cursor Marketplace; it only records that they are not part of this announcement and were never in the cited source.

Sources

• Cursor, “Google Workspace Plugins”: https://cursor.com/changelog/google-workspace-plugins
• Cursor Marketplace, “Google Drive”: https://cursor.com/marketplace/cursor/google-drive
• Cursor announcement on X, August 3, 2026: https://x.com/cursor_ai/status/2084376701539405904
• Cursor, “How Notion used the Cursor SDK to embed coding agents”: https://cursor.com/blog/notion

Provenance. Every claim on this page was re-verified against Cursor's anchored changelog entry and the Drive Marketplace listing on 2026-08-09. The X post is cited as the original announcement only; it answers automated fetches with HTTP 200 and a JavaScript shell containing none of the post text, re-checked August 31, 2026, and is not the sole source for any claim here.