Concepts
How registry adapters work
Registry sources are compiled into MCPOrbit, not loaded from a folder. Adding one is a source change and a rebuild, so it is not something you can do from the app you downloaded.
MCPOrbit reads server listings through registry adapters. An adapter owns everything about one source — its base URL, auth, pagination style and response mapping — and the interface it implements commits to a single method, fetchPage, which returns a page of servers and an optional cursor. Two adapters ship: the official MCP Registry and Smithery.
The set of adapters is a fixed array in the app's source. Adding a source means writing a class that implements the adapter interface in its own file, importing it alongside the others, appending an instance to that array, and rebuilding the app. There is no adapters folder, nothing scans a directory at runtime, and an adapter that is not in that array never reaches Settings to be switched on.
What Settings, then Registries, controls is which of the compiled-in sources are enabled. Every adapter is enabled by default, and disabling one stops the Server Browser from querying it.
MCPOrbit ships as a signed application and its source is not published, so writing an adapter is not a procedure you can follow against the download. This page describes how the layer is built, not a change you can make yourself.
