We submitted the Speko plugin to the first-party marketplace on 20 August via cursor.com/marketplace/publish and got the “Thanks for applying” confirmation page. Twenty-five days later there has been no email, and cursor.com/marketplace/plugins/speko still returns “Marketplace Plugin Not Found”.
We followed up to [email protected] on 30 August — no reply, and no bounce.
I’ve read Colin’s earlier answers here, so I understand review is manual and there’s no status page, and I’m not asking for a timeline. My question is narrower: can someone confirm the submission actually reached the queue? Since there’s no receipt, no ticket id and nothing visible after submitting, we have no way to tell the difference between “waiting” and “lost”.
Details, in case it helps someone look it up:
Plugin: Speko — voice agents, speech synthesis and transcription through our hosted MCP server
Submitted: 20 Aug 2026 · follow-up email: 30 Aug 2026
One clarification while I’m here. Kevin mentioned in another thread that cursor.directory is the home for community-built plugins, while the curated first-party marketplace skews toward company integrations. Speko is a company integration, so I assumed /marketplace/publish was the right venue — please correct me if we should be going through the directory instead.
Happy to resubmit if the original was lost. I’d just rather not create a duplicate entry by guessing.
Hey, thanks for the detailed report, and sorry for the silence on our side.
You picked the right venue. Speko is a company integration with a hosted MCP server, and that’s exactly what the curated marketplace at cursor.com/marketplace/publish is for. cursor.directory is a separate community system with its own queue, not a replacement, so you went the right way by using the form.
One important note: the “Thanks for applying” page only shows after the submission is accepted on our side, so please don’t resubmit. A second submission will just create a duplicate for reviewers.
I’ve asked the marketplace team to check your Aug 20 submission (handle speko, repo github.com/SpekoAI/cursor-speko, contact [email protected]) and confirm what stage it’s at. I’ll reply here as soon as I hear back.
In the meantime, you can also publish Speko on cursor.directory. It’s a separate system with its own queue, it won’t conflict with your marketplace submission, and you fully manage that listing yourself.
“Phone calls, transcription and speech through one Speko account: place and monitor real AI phone calls, transcribe audio, and synthesize speech, with each model picked from measured benchmarks.”
The listing is still on f2603b0. What’s the right way to request an update for an approved plugin? We don’t want to resubmit and create a duplicate. Thanks!
Hey, congrats on the launch. Glad Speko made it to the listing.
On the update, there’s no need to resubmit through the form. You’re right that it would create a duplicate. For the public first-party marketplace, updates don’t sync automatically from GitHub. Each update goes through a manual review on our side before it’s published. More details here: Marketplace security | Cursor Docs
Once we republish the listing, installed clients will pick up the new revision on the next restart or when the window comes back into focus. There’s no separate update command needed. That’s why the listing is still on f2603b0 and not 4571ba9.
I’ve asked the marketplace team to reindex your listing to the latest commit 4571ba9 in github.com/SpekoAI/cursor-speko, handle speko. The updated description will come with it. I’ll follow up here as soon as it goes through.
So it’s documented for future updates too, you can also send the request to [email protected] with the plugin name, repo, and the new commit you want to appear in the listing.
For the resync, please send the request directly to [email protected] with:
plugin name: speko
repo: github.com/SpekoAI/cursor-speko
the commit you want live: 4571ba9
That inbox is handled by the marketplace team, so it’s the fastest and most reliable path for this update and future ones. As you noted, there’s no need to resubmit through the form. That would just create a duplicate entry.
Updates to a first-party listing don’t sync from GitHub automatically. Each one goes through a manual review before it’s republished, which is why the listing is still on f2603b0. Once it’s republished, installed clients will pick up the new revision on the next restart or when the window regains focus.