Skip to Content
MosaicMosaicDocs

MCP Setup

Connect AI clients to the Mosaic MCP server.

Starter documentation. Features and account details may differ from this deployment.

Mosaic's MCP endpoint is:

Use the endpoint or installer configured for your Mosaic deployment.

The server is remote; no local process is required. Authentication happens through Mosaic's OAuth flow when the client connects. Sign in with Google, a code sent to your email, or a password. MCP access is available on every Mosaic plan, including Free.

Claude Code

Use the endpoint or installer configured for your Mosaic deployment.

Start Claude Code, use the mosaic MCP server, and complete the browser sign-in flow when prompted.

Codex CLI

Use the endpoint or installer configured for your Mosaic deployment.

Start Codex CLI, invoke the mosaic MCP server, and complete the OAuth login flow in the browser.

Connect from a remote machine

If your client runs on another machine, such as over SSH or in a container, a browser on your computer can't reach the client when sign-in finishes. Sign in like this instead:

  1. Start the login on the remote machine. For Claude Code, run claude mcp login mosaic --no-browser. For Codex CLI, run codex mcp login mosaic.
  2. Open the printed link in a browser on your computer.
  3. Select The app I'm connecting runs on another machine, then choose how to sign in.
  4. After you sign in, Mosaic shows a link and a curl command. If your client asks for a redirect URL, as Claude Code does, paste the link. Otherwise, run the curl command on the remote machine while the client is waiting, as with Codex CLI.

IDE / JSON Configuration

For editors that accept JSON MCP server config, add this under mcpServers:

Use the endpoint or installer configured for your Mosaic deployment.

Trigger a connection from the editor and finish the browser login flow.

On this page