Skip to content
Status

Connect · Catalog overview

Catalog overview

Browse third-party MCP servers from the MCP Registry and add them to a project as remote MCP sources.

The Catalog is a directory of third-party MCP servers, powered by the official MCP Registry. Browse it to find a server, then add it to a project as a remote MCP source. Open it from Catalog in the dashboard sidebar.

Access requirements

Section titled “Access requirements”

Browsing the catalog requires the project:read or mcp:write scope. Adding a server to a project requires the mcp:write scope. Both are included in the default Admin role. The Member role can browse the catalog, but the install flow enforces mcp:write before a server is added.

Browsing

Section titled “Browsing”

The full catalog loads in one response, so search, filtering, and sorting are instant. The toolbar controls the view:

  • Search matches on server name
  • Sort by offers Most Popular, Recently Released, Last Updated, A → Z, and Z → A
  • View as switches between a card grid and a table
  • The count shows how many servers match the current filters

Servers already added to the project are marked with an added state. Select several entries to add them in one action.

Filters

Section titled “Filters”

Six filter dimensions narrow the list:

FilterOptions
Auth typeNo Auth, API Key, OAuth 2.1, Other
SetupAutomatic (DCR), Manual setup
Tool behaviorRead-only only, Can modify data
Popularity100+ users, 1k+ users, 10k+ users
Last updatedThis week, This month, This year
Tool count5+ tools, 10+ tools

Filter state lives in the URL, so a filtered view can be bookmarked or shared.

Server details

Section titled “Server details”

Selecting a server opens its detail page, which covers:

  • The server name, its website or registry specifier, and badges for Official, Latest, and Manual Setup
  • About, the server description as published to the registry
  • Available Tools, listing every tool with its behavior annotations
  • Usage estimates for this week, the last four weeks, and all time
  • Version & Release details covering version, status, publish date, last update, and source
  • Registry details covering the registry name and the server specifier

A Manual Setup badge means the server does not support dynamic client registration. Connecting to it requires static OAuth client credentials or an API key.

Adding a server

Section titled “Adding a server”

Click Add on a server card or detail page, or select several servers and add them together. The install dialog then walks through configuration.

When a server publishes more than one endpoint, a Configure step appears first. Set the Server name and use Select endpoints to include to pick which endpoints to install.

The configure step collects any remaining setup:

  • Server name for each server being added
  • Upstream headers for servers that authenticate with an API key. Values are stored on the server and sent with every upstream request.

Header values are optional at this point. Skip the step and set them later on the Settings tab of the created server.

On confirmation, the platform creates a remote MCP server pointing at the selected endpoint, creates an MCP server with private visibility, and stages a default MCP endpoint so the server can serve straight away. Servers that support dynamic client registration have their OAuth configuration applied automatically.

Good to know

Private visibility keeps the endpoint gated behind a user session. This matters when upstream API-key headers are stored on the server, since a public endpoint would expose them to anyone holding the URL.

After the install completes, the dialog links to the next actions: Add more sources, Connect via coding agents, and Configure MCP settings.

Tools from a catalog server behave like any other tool source. Expose them on an MCP server alongside API tools and functions.

Removing a server

Section titled “Removing a server”

Open the server detail page and click Remove. Removal drops the server from the deployment and deletes every MCP server built from its tools, not only those built exclusively from them. Adding the same server again is always allowed, and Add another installs a second copy for cases such as separate credentials per environment or per tenant. Multi-tenant MCP walks that pattern.

Next steps

Section titled “Next steps”