Why Docker MCP Catalog submissions get rejected

What reviewers and the rules say

Stores that take plugins read them from a public GitHub repository at a pinned commit, and validate it before anyone reviews it. A private repository, a missing manifest, README or licence, a branch instead of a commit, or a failing CI run leaves nothing to review. Gemini CLI’s gallery skips a repository that fails validation without saying so.

How to fix it

• Host the plugin in its own public GitHub repository. A private monorepo can’t be pinned.
• Claude: add .claude-plugin/plugin.json, a README of at least 40 words and a LICENSE, then run claude plugin validate --strict.
• Don’t leave a SKILL.md at the root beside a skills/ folder. Claude loads it as a single-skill plugin and hides the rest.
• Grok: pin a full 40-character commit SHA, not main or a tag.
• Docker: use a licence that lets people run the server, such as MIT or Apache 2.0, and get CI green before asking for review.
• Gemini CLI: put gemini-extension.json at the root and add the gemini-cli-extension topic.

Caught by

• repo.public The plugin repository is publicmcplane CLI
• repo.claude-manifest .claude-plugin/plugin.json existsmcplane CLI
• repo.root-skill No root SKILL.md shadowing the plugin’s skillsmcplane CLI

Check your servermcplane docs

What reviewers and the rules say

Stores that take pull requests close one that adds something already in the catalog, or a second one for the same plugin. Updates go through the existing entry.

How to fix it

• Search the catalog and the open pull requests before you add an entry.
• To update a listed Grok plugin, bump its pinned commit instead of adding a new entry.
• Close your own older pull request when you open a replacement.

Caught by

No script can see this one. A server check rules out the mechanical causes first.

Check your servermcplane docs

What reviewers and the rules say

Some stores stop taking new entries without closing the door. A Docker maintainer said so on 8 August, quoted above; since then 639 more pull requests adding a server have been opened, and none has been merged (counted on 1 October). Cursor curates its marketplace and works directly with plugin authors it trusts.

How to fix it

• Read the latest maintainer comments in the queue before you open a pull request.
• Ask on your pull request whether it will be reviewed at all.
• List the server where intake is open, such as the official MCP Registry, which takes entries through its own CLI.

Caught by

No script can see this one. A server check rules out the mechanical causes first.

Check your servermcplane docs

What reviewers and the rules say

Some reviews end without an explanation. ChatGPT rejection emails have arrived with an empty details section, Claude’s old plugin portal showed “Rejected” with no notes, Grok and Docker maintainers often close pull requests without a comment, Gemini CLI’s crawler skips repositories silently, and Cursor’s publish form sends no confirmation.

How to fix it

• ChatGPT: reply to the rejection email with your case ID and ask for the specific finding.
• On a pull request, ask what would make it acceptable.
• Rule out the mechanical causes with a server check before you resubmit.

Of the 6 pull requests maintainers closed in the Grok and Docker queues we track, none had a comment saying why (checked 1 October).

Caught by

No script can see this one. A server check rules out the mechanical causes first.

Check your servermcplane docs