Viral∞p
AI plugin directories

How to list on Cursor Marketplace

Cursor plugins are how a product shows up inside the editor most startups already use. The marketplace is small enough that a well-made plugin gets noticed, and the install is two clicks from Settings. The bar is a public repo, a clean manifest and a remote MCP server that signs the user in instead of asking them to paste a key.

You ship

Public repo: .cursor-plugin/plugin.json, .cursor-plugin/marketplace.json, mcp.json, skills/

Submit at

cursor.com/marketplace/publish

Review

Manual review of every version; plugins must be open source

Auth

Remote MCP with OAuth dynamic client registration, no key to paste

01

The files

  • .cursor-plugin/plugin.json: name (unique, lowercase, kebab-case), displayName, version, description, author with name, email and url, homepage, repository, license, logo, keywords, category, tags, mcpServers pointing at ./mcp.json
  • .cursor-plugin/marketplace.json: name, owner, metadata and the plugins array, required when one repo holds several plugins and harmless when it holds one
  • mcp.json: the MCP servers block, for a SaaS ideally { type: "http", url: "https://yourdomain/mcp" }
  • skills/<name>/SKILL.md plus references, the same skill you ship to Claude
  • assets/logo.png committed to the repo, optional but the listing looks unfinished without it
  • Optional Cursor-only pieces: rules as .mdc files, agents, commands, hooks
02

Submit it

  1. 1Push the plugin to a public git repo. Every plugin on the marketplace must be open source.
  2. 2Check the manifest against the cursor/plugin-template repo; a valid .cursor-plugin/plugin.json with a unique kebab-case name is the gate.
  3. 3Submit the repository link at cursor.com/marketplace/publish.
  4. 4Wait for the manual review. Each update is reviewed again before it is published, so batch changes.
03

How users install it

Once listed, users open Cursor Settings, go to Plugins (Customize in the sidebar), search for your name and click Install at project or user scope. Chat has a shortcut too:

In the Cursor chat

/add-plugin <plugin-name>

Point the plugin at your remote MCP server with OAuth and dynamic client registration. Cursor prompts the user to sign in to your product and pick a workspace, and there is no key to copy. That one decision removes most of the support tickets a plugin generates.

04

What we learned shipping ours

  • Reuse the skill folder from the Claude plugin verbatim. The two formats differ only in the manifest and the MCP config file name.
  • Keep the sync script dumb: clone the plugin repo, replace everything except .git and LICENSE, commit if changed. It runs in CI after every release.
  • Mention an API key fallback in the README for users behind an SSO policy that blocks OAuth popups.
  • The author block wants an email. Use a monitored one; that is where the review questions arrive.

Vendor docs this guide is checked against

Listed is step one.
Being named is the job.

Assistants recommend the brands they keep seeing. Viraloop generates and posts your short-form content daily, so the model's answer about you stays current.

Start posting dailyAll directories

Want the short version?

Ask AI for a summary of Viraloop, what it automates for you, and how it compares to the alternatives.