plugmcp
Sign up
2026-10-16

What's new: publisher pages, not a proxy

Listings now open the publisher's URL, known servers sit first, and the top pages are filling in from GitHub READMEs.

A stack of printed pages unrolling on a dark desk, tied with teal thread, next to a row of metal tokens.
The pages were already out there. We are unrolling them onto the listing.

The directory used to talk as if every server lived on PlugMCP. That was the wrong shape. This week the public site points at the publisher, and hosting is a separate choice on the same page.

What changed on a listing

  • The install block is the publisher's URL or local command. It is not an mcp.plugmcp.ai address.
  • A second link, On PlugMCP, is there if you want to host a copy. That creates a new server. It does not claim the listing.
  • Known servers rank above raw stars. Context7, Firecrawl, and Exa sit in front of a repo that happens to have a huge star count.
  • The top listings now carry the README, a short feature list, and the tools the README actually names.

Why it was empty

The GitHub token was in place, and nothing was calling GitHub. The Railway service named Worker is an n8n worker, not the directory crawl, so the job log stayed empty. We ran the crawl for the most prominent servers by hand. Context7's page now shows its two tools, resolve-library-id and query-docs, and the URL from the README. Firecrawl's page shows the remote endpoint and the tool list from its README.

The rest of the catalog is still thin. A listing you open tomorrow may have a README, or it may still say the crawl has not reached it. That is the next job: run the same pass on a schedule, not once.

The quieter chrome

Sort is a text row again: Most used, Stars, New, Downloads. Category chips are the small rounded ones. Sign up is the blue button. The card hover stays, and the Off / Healthy marks are gone from the public grid.