Catalog and Discover
Taxonomy vs. browse surfaces, and how a listing goes from draft to published.
Catalog vs. Discover
These two API groups cover different things despite both sounding like "browsing":
- Catalog is taxonomy metadata used to build filter UIs - categories (with live published-listing counts) and the distinct set of tags in use. It returns no listing content itself.
- Discover is curated, public browse content: admin-picked featured bundles, rotating hero banner slides, and a paginated grid of public bundles. This is what powers the actual browse/landing experience.
How a listing gets published
A new MCP listing starts as a DRAFT. Submitting it
(POST /{listing_id}/submit) moves it to PENDING_REVIEW and opens a
publish request. An admin then approves or rejects that request; approval
flips the listing to PUBLISHED and makes it publicly visible. A
rejected listing can be edited and resubmitted.
Private and organisation-visibility listings skip this queue entirely and publish immediately - the review step exists specifically for listings going into the public catalog.
Collaborators
More than one user can co-manage a single listing. Each collaborator holds a role of either Maintainer or Contributor, separate from the listing's own owner - useful for a listing maintained by a small team rather than one account.
Where to go next
- Organisations for how org-owned listings differ from this review flow.
- Full endpoint list: Catalog, Discover, and MCP Listings in the API reference.