Submit for Spotlight

Submit your tool for a spotlight feature on the MCP Tool Shop catalog. Structured intake, CI validation, human review.

What qualifies

Your tool must be installable and runnable by a stranger. It needs a README with what it does, a quickstart, known limits, and a license. You must provide at least one proof link — a demo, test suite, benchmark, or reproducible command.

Our worthiness rubric A checklist that scores tools on documentation, tests, releases, and other quality signals. (minimum score: 3/5):

  • License is OSI-approved
  • At least 1 release published
  • README has install + usage
  • Activity within last 90 days
  • No known security issues

What disqualifies

  • No install path or unclear runtime requirements
  • "Coming soon" repos with no working code
  • No license
  • Claims with no proof ("10x faster" with no benchmark)
  • Tool already in the catalog

How to submit

  1. Fork the marketing repo.
  2. Create submissions/<your-slug>.json using the schema below.
  3. Open a PR using the "Submit for Spotlight" or "Submit for Experiment" template. GitHub will prompt you to choose.
  4. Wait for CI. The validation script checks your file automatically. A human reviews weekly and merges or requests changes.

Submission schema

Each submission is a single JSON file. Required fields are marked. 

{
  "tool": {
    "name": "My Tool",
    "slug": "my-tool",
    "repo": "https://github.com/org/my-tool"
  },
  "category": "devtools",
  "kind": "cli",
  "pitch": "A short description of what the tool does and why it matters.",
  "goodFor": [
    "Use case one",
    "Use case two"
  ],
  "notFor": [
    "Not intended for this"
  ],
  "proof": [
    {
      "label": "CI",
      "url": "https://github.com/org/my-tool/actions",
      "whatItProves": "Tests pass"
    }
  ],
  "install": "npm install -g my-tool",
  "quickstart": "my-tool init",
  "maintainer": {
    "handle": "@you"
  }
}

category: mcp-core, voice, security, ml, infrastructure, desktop, devtools, web, games

kind: mcp-server, cli, library, plugin, desktop-app, vscode-extension, homebrew-tap, template, meta

proof: at least 1 entry with label, url (https), whatItProves

goodFor: 1–5 items · notFor: 0–3 items (optional) · pitch: 10–200 characters

Two lanes

Spotlight

Your tool enters the spotlight queue. If it passes the worthiness rubric A checklist that scores tools on documentation, tests, releases, and other quality signals. , the pipeline generates a proof page, press kit, and snippets. A human reviews and publishes.

Experiment

Your tool enters the experiment pipeline for structured A/B testing. Useful for early-stage tools that need data before a full promotion.

Review policy

  • Submissions are reviewed on a weekly cadence.
  • Submissions may be marked needs info if we need clarification. Check the queue for reviewer notes.
  • We may ask for clarification or route early tools to experiments.
  • Rejections include a reason and a checklist of what to fix.
  • Resubmission is welcome after addressing feedback.
View submission queue · Trust Center