Cursor Workspace Plugins: Gmail, Drive and Calendar

The August 3, 2026 release added separate plugins for Google Drive, Gmail, and Google Calendar. They give Cursor agents tools for reading and changing workspace data through an authorized Google account. The connection is useful when project context lives in a design brief, an email thread, or a meeting schedule rather than in the repository itself.

Each pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. has its own action surface. Drive covers files and folders, Gmail covers messages and threads, and Calendar covers schedules and events. Installing one does not imply the other two are connected. That separation is helpful: a coding workflow that only reads product documents does not also need the ability to send mail or change a calendar.

Open Cursor Marketplace or the Customize page, choose the specific Google pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition., and complete the account authorization flow. Read the requested Google permissions before accepting. Then start a narrow test in an account or folder where an incorrect write is recoverable. A successful connection proves that the tool can act; it does not prove that every available action belongs in your normal agent policy.

1. 1Choose Drive, Gmail, or Calendar from Cursor Marketplace or Customize.
2. 2Review the Google account and permission scopes shown during authorization.
3. 3Connect the least privileged account that can complete the intended workflow.
4. 4Run one read-only request and inspect the returned file, message, or schedule context.
5. 5Test a reversible write, then decide whether higher-impact actions should remain available.

Keep the first prompt explicit. Name the Drive folder, mailbox query, calendar, or date range, and say whether the result should be a draft or an external action. Broad instructions such as clean up my inbox hide several decisions in one sentence. A bounded request gives you a result that can be compared against the source and makes an unexpected permission easier to spot.

The strongest workflows connect a concrete workspace artifact to a checked engineering output. Ask Drive for the current product brief before building a feature, search Gmail for a customer's exact reproduction steps, or read Calendar availability while drafting a release review. The agent should cite the item it used so a reviewer can distinguish source context from an inference made during the task.

Writes are useful once the source-reading step is dependable. An agent can create a Drive summary after a release, draft an email that links the pull request and its checks, or propose a Calendar event after it finds free time. I would keep the first version in draft state. Sending or scheduling is a separate decision with a real audience, and it deserves a person or a tested approval rule.

These examples are patterns, not claims that Cursor ships a prebuilt workflow with those names. The pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. supplies the documented actions. Your prompt, rules, hooks, and review process decide how they are combined and which result counts as complete.

Treat each connection as access to live company data. Google permissions, the chosen account, and any Cursor team controls form the outer boundary. Prompts and rules can guide behavior, but they are not a hard substitute for removing an unneeded capability. If an agent should never send email, do not rely on the word draft alone. Keep send permission unavailable or put the action behind a deterministic approval control.

Separate reading from acting in both the prompt and the review record. First collect the source items and proposed change. Then approve the Drive write, Gmail send, label change, or Calendar update. This two-step pattern is slower by one turn and much easier to audit, particularly when a thread includes private recipients or an event change affects people outside the project team.

The launch note describes actions, not delivery guarantees, retention terms, or a complete enterprise control matrix. It does not say every Google file format is parsed equally, that a sent message can always be recalled, or that a calendar edit will satisfy your organization's scheduling policy. Test the exact file type and action your workflow depends on, then keep the Google audit record where your administrators normally review it.

Plugins also do not make workspace data repository truth. A Drive brief can be outdated, an email can contain a tentative answer, and a calendar title can omit the real decision. Ask the agent to link or identify its sources and let the repository tests, pull request review, and named owner settle the engineering result. External context should improve the task without quietly becoming an authority it was never meant to be.

Plan for revocation as part of setup. Record which Google account was connected, which pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. uses it, who owns the workflow, and how access is removed. Then test the removal path with a noncritical connection. An integration inventory is useful only if an administrator can turn an obsolete credential off without searching through old agent chats.

When a workflow fails, preserve the pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. error and the exact action requested. A missing Google permission, an unavailable file, and an agent reasoning error need different fixes. Reauthorizing broad access may hide the symptom while increasing the account's exposure, so diagnose the failed boundary first.