What we are building
A catalog of MCP servers you install from the publisher, and a separate place to host the ones you actually run.
PlugMCP is two products that share a database. The public site is a catalog of other people's MCP servers. The gateway is only for a server you decide to host. Mixing those up is how a directory starts pretending to be the product.
The catalog
A listing is a card. It names the server, shows the publisher, and gives you their URL or their local command. Context7 is https://mcp.context7.com/mcp. Firecrawl is https://mcp.firecrawl.dev/v2/mcp. You put that address in Cursor, Claude, or whichever client you already use, with their credentials. PlugMCP does not sit in the middle of that call.
The cards are filled from public catalogs: the official MCP registry, GitHub, npm, PyPI, Docker Hub, and Smithery. A later pass reads the publisher's README so the page can show what the server actually does, which tools it exposes, and the real endpoint. Known products rank first. Star count alone was promoting anything loud.
The host
Hosting is the second path, and it is optional. When you want our keys, logs, and uptime, you sign in and create a server. HTTP tools run on the gateway. App and OAuth tools run as a workflow on n8n, reached only by the gateway. A wrapped server proxies a URL you saved, with the credential you saved. None of that is the official install for a third-party listing.
Browser tools stay on your machine. The gateway never sees those cookies.
What this is not
We are not a proxy marketplace. A badge that says a server is listed here is not an install path. The install path is the publisher. If you want a copy on PlugMCP, that is a new server you create, with a slug of its own.