MCP servers

Settings › MCP › Marketplace searches every server published to the official MCP Registry. Verified servers sit on top and add in one click with a browser sign-in. Every other card shows who published it, whether it runs on the web or on this computer, and its logo.

The catalog is kept on your computer and refreshed in the background, so the marketplace still works when the registry is slow or offline. In the CLI, /mcp → b searches it; in the editor extension, Browse does.

• A web server (a public https address) is saved to your account, so the app, the CLI, your editors and the Chrome extension all have it.
• A command, or an address on this computer or your network, stays on this computer for that folder, shared by the app, the CLI and your editors.

There is a limit on how many servers are on at once, counting both kinds; one added past it is added switched off and says so.

Paste a URL, a command, or the mcpServers block from Claude Desktop, Cursor, VS Code or Zed (or import the file), and each server goes where it belongs. A URL is checked for how it signs in (a browser sign-in, a key, or nothing), and a server that needs a key asks for it.

The same box is /mcp → a in the CLI (it also takes a config file's path) and Add in the editor extension. Servers you already set up in another tool show under "Found on this computer" with an Add button.

Star a server in the marketplace, or ask the AI to make it a default, and it shows up, ready to connect, in the chat's settings menu of every workspace, new ones included. A default is offered, never added on its own: nothing connects until you press Connect.

In the CLI and editors without an Atlarix panel, /mcp lists your defaults.

If a question or task needs a service you haven't connected, Atlarix searches the registry and suggests it: a "Recommended for you" card above the box in the app, the editor extension and the Chrome extension, or a Connect / Not now prompt in the CLI and other editors. Connect adds it and signs you in, and the agent carries on.

MCP tool calls get the same per-tool approval as the agent's other actions, and the chat names what each one used. In the Chrome extension, Atlarix asks before every call to a connected service, so a web page can never get the agent to act on your accounts without your yes.