# How to get your MCP server into the Cursor Marketplace

Cursor has two places to be listed, and they don't share a queue. The official Cursor Marketplace is hand-picked, open source only, and mostly for companies. The community-run cursor.directory is self-serve and usually live the same day. Anyone can also install your server from a link, listed or not.

## The official Cursor Marketplace

Cursor launched its marketplace on February 17, 2026, with plugins from Amplitude, AWS, Figma, Linear and Stripe ([Cursor](https://cursor.com/blog/marketplace)). By November 2026 it listed about 490 plugins ([AI Tools Radar](https://woojinahn.github.io/ai-tools-radar/cursor/)).

### Who gets in

- **Mostly companies.** Cursor says the marketplace is curated with "a small group of trusted partners" for now, and every plugin and every update is reviewed by hand ([Cursor](https://cursor.com/help/security-and-privacy/marketplace-security)). Cursor staff point individual developers to cursor.directory instead ([Cursor forum](https://forum.cursor.com/t/cursor-plugin-submission/166867)).
- **Open source.** The code has to be in a public Git repository.
- **Free.** Under the [publisher terms](https://cursor.com/marketplace-publisher-terms), your plugin has to be free to Cursor users, with no fees "directly or indirectly". A plugin that needs a paid account with you is a gray area the terms don't address.
- **Permissive licenses only:** MIT, BSD or Apache 2.0. Anything under GPL, AGPL or LGPL can't be included.
- **Verified.** Cursor checks "your identity and business legitimacy" and reviews your code. It can reject you for any reason and doesn't have to say why.

### What to submit

A plugin, in one of two layouts ([Cursor](https://cursor.com/docs/reference/plugins)):

- A `plugin.json` at the root with the open Agent Plugins `$schema`, or
- A `.cursor-plugin/plugin.json`.

Either way, your MCP server goes in an `mcp.json` at the plugin's root. Use `${CURSOR_PLUGIN_ROOT}` for paths, because Cursor doesn't expand the standard's `${PLUGIN_ROOT}`. Declare every `${VARIABLE}` under `variables` and keep the values out of the repo.

Cursor's checklist before you submit:

- A valid manifest with a unique, lowercase, hyphenated `name` and a clear `description`
- A README that explains how to use and configure it
- Only relative paths, none starting with `..`
- A logo committed to the repo
- Tested locally, from `~/.cursor/plugins/local`

Then send the repository link at [cursor.com/marketplace/publish](https://cursor.com/marketplace/publish). A repository with several plugins needs a `.cursor-plugin/marketplace.json`.

### How long it takes

Cursor staff say review "typically" takes one to two weeks ([Cursor forum](https://forum.cursor.com/t/plugin-marketplace/160943)). What people report is slower:

- **No confirmation.** You won't get an email saying it arrived, and there's no status page.
- **Often a month or more.** ZoomInfo heard nothing for a month despite several emails ([Cursor forum](https://forum.cursor.com/t/pending-review-zoominfo-plugin-submission-no-response-after-1-month/164579)), and other teams have waited three weeks or more with no reply.
- **Don't submit again.** Staff ask people not to resubmit, because it creates duplicates ([Cursor forum](https://forum.cursor.com/t/marketplace-plugin-submission-pending-since-sep-24-no-response/174417)). After about three weeks, email marketplace-publishing@cursor.com instead ([OpenApps](https://theopenapps.com/blog/how-to-publish-a-cursor-plugin)).

Updates aren't pulled from your repo automatically. After a change, ask Cursor to re-index your plugin.

### A second way in: the Grok Bot form

Since October 2026, xAI's plugin form at [x.ai/bot/marketplace/submit-a-plugin](https://x.ai/bot/marketplace/submit-a-plugin) lists plugins in Grok Bot and Cursor (Cursor [became part of SpaceX](https://cursor.com/blog/joining-spacex) in August 2026). It takes an MCP URL or a public GitHub repo, a 600-character description and testing instructions, and submitting accepts Cursor's publisher terms ([MCP Tower](https://mcptower.com/blog/submit-plugin-to-grok)). It's not clear whether it shares a queue with Cursor's own form.

## cursor.directory

[cursor.directory](https://cursor.directory) is the community marketplace that Cursor itself points to. It's quicker, and you manage the listing yourself ([cursor/community-plugins](https://cdn.jsdelivr.net/gh/cursor/community-plugins@main/README.md)):

1. Go to [cursor.directory/plugins/new](https://cursor.directory/plugins/new) and sign in with GitHub or Google.
2. Paste your GitHub repository. It finds `.mcp.json`, rules and skills on its own, or you can fill in the details by hand.
3. An AI agent scans a fresh copy of the repo for malware, prompt injection, spam, impersonation and low quality. If it decides the plugin is safe, it goes live with no person involved. Flagged plugins stay hidden until someone reviews them.

Admins can give a verified badge if you ask. Scans sometimes fail or get stuck: in September 2026, 18 plugins sat on "Scan failed" and one flagged plugin stayed hidden for more than two weeks ([Manycp](https://manycp.com/directories/cursor-directory)). Submissions are rejected for a private repo, no plugin components found, or a name or repo that's already listed.

## Install links work without a listing

Anyone can add your server with a link, whether you're listed or not ([Cursor](https://cursor.com/docs/plugins)):

```
cursor://anysphere.cursor-deeplink/mcp/install?name=NAME&config=BASE64_CONFIG
```

The config is your server's JSON settings, encoded in base64. In a README or on a website, use the `https://cursor.com/install-mcp` form of the link, which works where `cursor://` links don't. Never put an API key in the config: anyone with the link can read it.

Put an "Add to Cursor" button in your README and docs while you wait for review.

Checkers to run before you submit, and companies that will submit for you, are in the [overview](https://submitmcp.com/guides).
