Repository navigation
Stale pre-migration submission blocks re-listing: scalixworld/scalix-cloud-mcp #422
Description
Hi team,
We submitted our plugin repo (https://github.com/scalixworld/scalix-cloud-mcp) through the previous cursor.directory submission flow on 20 July 2026. It confirmed receipt (scan queue) but never went live - searching the directory for "scalix" returns no results today.
Since the relaunch under the Open Plugins standard, attempting to resubmit the same repo via /plugins/new fails with "A plugin with this name or repository already exists" - so the pre-migration record appears to survive as an unpublished row that blocks the repo slot, with no way for us to manage or publish it from an account.
Could you either publish the existing entry or clear the stale record so we can resubmit cleanly through the new flow?
Listing details, for reference:
- Name: Scalix Cloud
- Repo: https://github.com/scalixworld/scalix-cloud-mcp (conforms to Open Plugins; auto-scan detects the MCP server component correctly)
- Component: hosted remote MCP server (HTTP), https://api.scalix.world/v1/mcp
- Also listed in the official MCP registry as world.scalix/cloud
Happy to provide anything else needed. Thank you!
Activity
Scalix-World-team commentedon Aug 7, 2026
Checking in a week on. Unless this was cleared in the last few days, the pre-migration row for
scalixworld/scalix-cloud-mcpstill holds the slot: resubmission is rejected with "a plugin with this name or repository already exists", and the entry is not visible on the directory, so there is nothing for us to edit or delete from our side either.The Cursor marketplace team said on 31 July they were flagging it for the directory team.
Two things that might make this easier:
Repo is public and current: https://github.com/scalixworld/scalix-cloud-mcp
deanrie commentedon Oct 5, 2026
Hey, thanks for the detail and apologies for the silence since July. A submission that went through the old flow and confirmed receipt but never went live can't be unstuck from the owner side; there's no resubmit that bypasses the stale queue entry, and a fresh submission of the same repo collides with it. That needs the directory team to clear the old record. I've passed
scalixworld/scalix-cloud-mcpalong with the July 20 submission date so they can find it. I'll update here when it moves.