Out of the box, Cursor’s agent reads your repo and writes code. That’s enough to be useful, but not enough to check the current docs, read a failing CI log, or look at the production error your user just hit. Plugins close that gap — and since Cursor launched its plugin marketplace in February 2026, the catalog has grown past the point where anyone should install indiscriminately.
A recent Firecrawl blog post by Eric Ciarla went through the marketplace listings, read each plugin’s source, and kept twelve. It’s a useful filter if you’re setting up a new machine this quarter.
What a plugin actually is
Per Cursor’s plugin docs, a plugin bundles any mix of six components: rules (persistent .mdc guidance), skills (instructions loaded when a request matches), subagents, slash commands, MCP servers, and hooks that fire on events like session start. Two formats coexist: the open Agent Plugins standard and Cursor’s own format with a .cursor-plugin/plugin.json manifest. The install flow is the same either way.
The key distinction: a plugin is an instruction layer over a plain MCP server. Its skills and rules tell Cursor when to reach for each tool, which means the tool gets invoked at the right moment more often.
Installation is one line from chat — /add-plugin firecrawl — or via the Customize panel, where you pick project or user scope. Project scope matters more than it sounds: you probably don’t want a deploy or database plugin available in every repo you touch.
The shortlist that matters
The twelve fall into a few clusters:
- Grounding the agent in reality. Firecrawl gives Cursor live web search with full page content, crawling, browser interaction, and document parsing. GitHub connects repos, issues, PRs, and Actions logs. These fix the two biggest sources of bad agent code: stale assumptions about an API, and missing context on why a function looks the way it does.
- Process discipline. Jesse Vincent’s Superpowers ships 14 skills covering brainstorming, TDD, systematic debugging, and a session-start hook so the method loads without being asked. pstack, from Cursor engineer Lauren Tan, is the heaviest entry at 51 skills plus two subagents — its real value is forcing you to define what “done” means before the agent starts. Thermos runs parallel correctness and quality reviews on your branch.
- Services and environment. Sentry, Supabase, Vercel, Linear, and Figma each wire one production surface into the editor. Chrome DevTools for Agents handles real browser debugging. Supermemory persists context across sessions.
One broader signal: Cursor supports the open Agent Plugins standard, so plugins built to that spec load in other agents too. Building your workflow around the spec rather than a single editor is cheap insurance.
Worth knowing before you install
Every marketplace plugin is manually reviewed and must be open source, and updates are reviewed too. Teams and Enterprise admins can run a private marketplace with Default On or Required settings.
Costs show up at the edges. Firecrawl’s free tier is 1,000 credits a month — fine for scraping docs pages, not for large crawls — and the first run has a setup delay while the install rule configures the CLI. pstack assumes access to multiple frontier models, so multi-model workflows mean multi-model spend. Loose prompts on the GitHub plugin can trigger wide searches, and its write actions run as you, so read proposed comments before approving.
The Firecrawl plugin leans on a broader data layer — its Developer Index covers 70M+ artifacts and, per the post, related Alexandria data providers are headed into the plugin too. I wrote about one endpoint that now reaches providers, not just pages, if you want the direction of travel there.
Practical next step: install Firecrawl and GitHub first — they cover the highest-frequency failure modes — then add Superpowers or pstack depending on whether your bottleneck is planning or review. Skip the rest until a real task asks for it.