Connect · Catalog
Catalog
Discover and import official third-party MCP servers from the MCP Registry.
The Catalog page discovers official third-party MCP servers and imports them into the project. It’s powered by the official MCP Registry. Open it from Connect > Catalog in the dashboard.
Access requirements
Section titled “Access requirements”Viewing this page requires the project:read or mcp:write scope. Adding a catalog server to the project requires the mcp:write scope. Access is included in the default Admin role; the Member role can browse the catalog, but adding a server requires mcp:write, which is enforced in the install flow.
Browsing
Section titled “Browsing”Browse servers as cards or a table. Search by name, filter by category, and sort by most popular, recently released, last updated, or name. Servers already added to the project show an added state. Select multiple servers to add them in one action.
Server detail
Section titled “Server detail”Each catalog entry has a detail page:
- The server’s name, badges (official status, latest version, manual setup), website, and an about section
- Available Tools — every tool with read-only, destructive, idempotent, and write annotations, with expandable descriptions
- Usage estimates (weekly, monthly, all time), version and release details, and registry information
Add or remove the server from the project directly from the detail page.
What an install creates
Section titled “What an install creates”Catalog entries install as remote MCP servers. The vendor keeps running the server, and the Control Plane registers its URL and proxies sessions to it, adding authentication, per-tool access control, and tool logs in front. Nothing is copied or re-hosted.
One entry can create several servers, because an entry can publish more than one remote endpoint. The install dialog lists them and creates one server per selected endpoint, after discarding endpoints that do not use streamable HTTP.
Installing an entry that is already in the project is also allowed. It creates another independent server, which is how one vendor maps onto several tenants. Multi-tenant MCP covers that pattern. Remote MCP servers covers the install flow, upstream headers, and what to do about entries marked Manual Setup.