What MCPOrbit asks on first launch

On first launch, MCPOrbit walks you through four screens: a welcome, a theme picker, a form headed Add your first connection, and a short confirmation. The middle two carry a Back button, so nothing you pick on the way through is final.

The welcome screen is a line about what MCPOrbit is and a Get Started button.

The theme picker offers Light, Dark, and System. Your choice applies straight away, and Settings has the same control if you change your mind later. Back returns to the welcome, Next moves on.

The third screen asks for a Name and a Type. Type is three buttons: STDIO for a server that runs on your own machine, HTTP or SSE for one you reach over the network. STDIO is already selected.

A STDIO server gets a single field here, labelled Command, with npx @modelcontextprotocol/server shown in it as a placeholder. There is no Arguments field on this screen, so a server that needs arguments cannot be finished from the wizard. Skip it and add that server afterwards from Add Connection in the sidebar, which has both fields. An HTTP or SSE server gets a URL field and nothing else; the Auth control lives in the sidebar form, not here.

Name does not fill itself in. Type one.

Three buttons close the screen: Back, Skip, and Add & Continue. Add & Continue saves the connection and moves on. Skip moves on without saving anything. Add & Continue stays dim until Name has something in it, and Name alone releases it, so a connection with an empty Command can still be saved from here. Pressing Enter does nothing on this screen; use the button.

The last screen confirms you are set up and ends onboarding. Skipping costs you nothing. Add Connection at the bottom of the sidebar opens a fuller version of the same form, with Arguments, Environment Variables, Roots, and a few other options on it.

MCPOrbit does not collect telemetry yet, so there is nothing about it on these screens and nothing to switch off. The telemetry page under Privacy lists what would be collected if it ships.