cursor / cursor/community-plugins

Delete shows "Plugin deleted." toast but the plugin stays live

Open
#413 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4k
Forks
671
Avg merge
3h 42m
Merged PRs (30d)
1

Description

Summary

Deleting a plugin from the cursor.directory dashboard shows a success toast ("Plugin deleted.") but the plugin remains live afterward.

Plugin: firmaradar-mcp (a remote MCP server)

Steps to reproduce

  1. Open the plugin's menu → Delete.
  2. A toast confirms "Plugin deleted."
  3. Reload the directory → the plugin is still listed.

What I've already checked

  • It still appears in an incognito / logged-out window, so it's server-side — not my local cache.
  • It persisted overnight, so it's not just propagation lag.
  • The listing shows "1 install" (not mine — I don't use Cursor myself).
  • The menu also shows a greyed-out "Verification requested" state and an "Unpublish" option, in case either is relevant.

Expected

Delete actually removes the listing.

Ask

Could you remove the firmaradar-mcp listing? I've re-submitted an updated version and want to avoid a duplicate. Happy to share any internal IDs / the dashboard URL if that helps. Thanks for maintaining the directory! 🙏

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the dashboard plugin Delete flow for firmaradar-mcp, then trace the server-side deletion and listing persistence. No files or tests are named in the issue. Done means deletion removes the listing after reload and from an incognito or logged-out window, without affecting the replacement submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.