Cursor releases 31 official plugins linking Gmail, Salesforce and more

Cursor is an editor that lets users pick from third-party models — Anthropic's Claude, OpenAI's GPT, Google's Gemini — while also training its own in-house model, Composer. This new plugin repository reads as a standardized gateway to external work tools that works the same way no matter which model is running inside the editor.

31 plugins split across categories

The repository lists 31 confirmed plugins. Developer tools make up the largest share, followed by work-integration tools for sales, HR, and legal.

Category	Count	Share
Developer Tools	12	39%
Integrations	15	48%
Productivity	3	10%
Utilities	1	3%

The Productivity category holds three plugins — Gmail, Google Drive, and Google Calendar — that let an agent handle search, reading, drafting, and scheduling on the user's behalf. The Integrations category spans 15 tools, from CRM and sales platforms like Salesforce, HubSpot, Gong, and Clay to Zoom, Intercom, DocuSign, Ashby, Navan, and Circleback. The GitHub and Playwright plugins also fall under this category, extending the same connection model to repository management and browser automation.

Developer tools with quirky names

The Developer Tools category features several plugins with names that stand out. Thermos, described as doing "thermonuclear branch review," audits security and correctness using parallel sub-agents, while Ralph Loop implements an iterative self-referential loop using what it calls "the Ralph Wiggum technique." Orchestrate splits large tasks into planner, worker, and validator roles and distributes them across multiple cloud agents, and Continual Learning selectively curates high-signal entries to incrementally update an AGENTS.md file. The one plugin on the list not built by Cursor itself is pstack, created by Lauren Tan — a sign that the repository accepts community contributions and isn't limited to in-house tools.

Overlap with OpenAI's 'Agent Plugins' standard

As covered in Cursor Joins AWS, GitHub and Others to Publish an Agent Plugin Standard, OpenAI's developer account announced the open "Agent Plugins" standard on August 6, reportedly with AWS, Cursor, GitHub, and Vercel participating in its development. That standard focuses on packaging Agent Skills and supporting MCP server configuration in a shared format. Whether the cursor/plugins repository is a direct implementation of that standard can't be confirmed from what's available here, but the structure of bundling and distributing skills and tools around a manifest overlaps with the standard's stated direction.

How to try it

Based on the repository's structure, developers have two paths for working with these plugins.

1. Check an existing plugin — Open the folder for the tool you want at the repository root (for example, gmail, salesforce, or zoom), and you'll find a .cursor-plugin/plugin.json manifest inside. This file contains the name, description, and category, and the descriptions shown in the table above are taken directly from what's published on the Cursor marketplace.
2. Build your own plugin — The create-plugin folder in the repository, described as a tool to "scaffold and validate a new agent plugin," automatically sets up the structure needed for a new plugin. Developers use it to generate the folder and manifest, then fill in skills for their own work tools.

Details on availability by country or pricing tier, and the exact menu location for opening the marketplace inside the Cursor editor, aren't covered in the source material and would need to be verified separately. Still, the repository itself is public, so developers can freely inspect the manifest format and the code of existing plugins.

Editor's take

This isn't the first time a code editor has reached into email and CRM territory. But there's a difference in Cursor bundling more than 15 work tools — Gmail, Salesforce, Zoom, DocuSign among them — into a single repository under one manifest format. In the past, connecting a work tool to an editor meant finding a separate extension for each service and registering API keys individually; now it's been consolidated into a single spec, .cursor-plugin/plugin.json, where you just pick from a list and turn things on. That signals Cursor's shift from being "an editor that writes good code" to becoming "a gateway agent that handles entire workflows."

Rather than deploying this repository straight into production, domestic development teams would do well to first pull apart the manifest structure. Building a trial plugin for an internal groupware system or in-house CRM using create-plugin will give a feel for which fields are required and what permission model is expected. In particular, for plugins that touch sales data — Salesforce, HubSpot, Gong — teams should get in the habit of scoping access permissions narrowly from the start to avoid incidents.

Viewed through the lens of a standardization race, it's hard to call it a coincidence that Cursor, AWS, and GitHub all signed onto the OpenAI-led Agent Plugins standard, and just two weeks later Cursor's own plugin repository hit Trending. It's likely that within the coming weeks, GitHub Copilot or other agent clients will announce support for the same manifest format. Once the pattern of building one plugin and using it across multiple agents takes hold, the custom integration code each service has built separately until now will likely be up for cleanup by next quarter.