What to prepare

  • A correctly packaged plugin, verified publisher identity and appropriate organization permission.
  • Supported MCP authentication and domain verification for a hosted server.
  • Test cases, reviewer access where required, assets and policy attestations.

A reviewed product integration

Public distribution requires an actual plugin package and an authorized verified publisher. Hosted MCP connections undergo setup checks; review also needs tested scenarios and supporting materials. Approval and the owner’s publication action are separate from uploading a package. This is an owner portal workflow, not a repository-list PR.

Submission workflow

  1. Prepare and validate the complete plugin package.
  2. Upload through the authorized organization and resolve reported findings.
  3. Complete connection, domain verification and review materials in the portal.
  4. Submit for review; publish the approved package when the owner authorizes it.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • Missing publisher verification, review materials or package assets.
  • Unsupported authentication, failed connection checks or missing policy attestations.

Primary sources

Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.

← Compare all destinations