Cursor Workspace Plugins: Gmail, Drive and Calendar

They are three separate plugins, for Google Drive, Gmail and Google Calendar, released on August 3, 2026. Each gives Cursor agents tools to read and change workspace data through an authorized Google account. They help when project context lives in a design brief, an email thread or a meeting schedule instead of the repository.

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 actions. Drive covers files and folders, Gmail covers messages and threads, and Calendar covers schedules and events. Installing one doesn't connect the other two, so a coding workflow that only reads product documents doesn't need the ability to send mail or change a calendar.

Install 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. from the Customize page in Cursor or from its Marketplace listing. In Customize, find the plugin, select Install, and choose a project or user scope. Each listing also gives a one-line install, such as /add-plugin gmail. Then complete the Google account authorization, and read the requested permissions before you accept.

1. 1Choose Drive, Gmail or Calendar in Customize or on the Marketplace.
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 file, message or schedule context it returns.
5. 5Test a reversible write, then decide whether higher-impact actions should remain available.

A successful connection proves the tool can act. It doesn't prove that every available action belongs in your normal agent policy, so run the first test in an account or folder where a wrong write is recoverable.

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. A broad instruction such as "clean up my inbox" hides several decisions in one sentence. A bounded request returns a result you can compare against the source, and an unexpected permission is easier to spot.

The useful ones connect a concrete workspace item to an engineering output you can check. Ask Drive for the current product brief before you build a feature. Search Gmail for a customer's exact reproduction steps, or read Calendar availability while you draft a release review. Have the agent cite the item it used, so a reviewer can tell source context from an inference made during the task.

Writes are useful once the 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.

Keep that first version as a draft. Sending or scheduling reaches a real audience, so it needs a person or a tested approval rule.

These cards are our own patterns. 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, and your prompt, rules, hooks and review process decide how they combine and which result counts as complete.

Treat each connection as access to live company data. The outer boundary is set by Google permissions, the account you chose and any controls your Cursor team applies. Prompts and rules can guide behavior, but they don't replace removing a capability you don't need. If an agent should never send email, don't rely on the word "draft". Keep send unavailable, or put it behind a deterministic approval control.

On Teams and Enterprise plans, admins can manage plugins through a team marketplace. 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. there is set to Default Off, Default On or Required, and developers can't uninstall a Required plugin. Those modes decide whether a plugin is installed, not which of its actions an agent may use.

Separate reading from acting, in the prompt and in the review record. First collect the source items and the proposed change. Then approve the Drive write, Gmail send, label change or Calendar update. The split costs one extra turn and leaves an approval you can audit. It matters most when a thread includes private recipients or an event change affects people outside the project team.

The launch note lists actions. It says nothing about delivery guarantees, retention terms or a complete enterprise control matrix. It doesn't say that 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, and keep the Google audit record where your administrators already review it.

Workspace data also doesn't become the truth about the repository. A Drive brief can be out of date, an email can carry a tentative answer, and a calendar title can leave out the real decision. Ask the agent to link or name its sources. Then let the repository tests, pull request review and a named owner settle the engineering result.

Plan for revocation during 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 on a noncritical connection. An integration inventory only helps if an admin can turn off a stale credential without digging through old agent chats.

When a workflow fails, keep 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 each need a different fix. Reauthorizing with broad access may hide the symptom while it widens the account's exposure, so find the boundary that failed before you change any access.