The MCP Registry is the internal catalog of Model Context Protocol (MCP) servers your team can plug into their AI editors. Anyone in your organisation can browse it, pick a server, and copy a client config snippet — no more sharing URLs and tokens in chat.

Open it at /mcp/registry or via the MCP Fleet area of the sidebar.

What you see

A card grid of every MCP server that:

• has been marked Public (listed in the registry) when it was registered, and
• is currently reachable (not in a down state).

Each card shows the server name, a short description, transport (stdio, SSE, HTTP, streamable-HTTP) and the list of tools it exposes.

What you can do

• Browse the catalog by name.
• Copy a client config snippet for the editor you use — Claude Desktop, Cursor or Windsurf — directly from the server card.
• Open a server’s detail page to see full metadata, health history and every tool it exposes.

How it works

The registry is a view onto the same MCP servers that appear in the MCP Fleet — the only difference is the filter. To make one of your servers appear here, tick List in registry when you register it (or edit an existing server).

Reachability status comes from the same health probes that power the fleet view. A server that goes fully down is hidden from the registry so nobody picks up a snippet that won’t work; a degraded server is still shown.

Connecting a client

Each server card offers install snippets for the common MCP-capable AI editors. Paste the snippet into your editor’s MCP config file, restart the editor, and the server’s tools appear.

Tip

For local, per-server MCP access over SSH (no cloud roundtrip), use the MCP Tailnet Manager desktop app. It opens a local bridge and generates snippets for the same editors.

Related

• MCP Fleet — the full inventory, including servers that aren’t in the registry.
• MCP Server tool — the standalone HostAtlas MCP bridge for talking to your HostAtlas tenant from an AI editor.
• MCP Tailnet Manager tool — local MCP bridges to your servers over SSH.