Connect Gemini CLI

Connect Gemini CLI to The Cloud with one terminal command. Browser sign-in runs once and there is no JSON file to edit.

Connect Gemini CLI

Gemini CLI registers MCP servers from the command line. One command adds The Cloud and opens your browser to sign in. After that, Gemini reads your Memory and acts in your workspace from any directory.

Before you start

A Cloud account. Create one at thecloud.so. The connection signs in as you, so the account has to exist first.
Gemini CLI installed, and a terminal where gemini runs.

The one address

There is a single MCP server address. It speaks HTTP JSON-RPC 2.0. You will paste it once:

https://mcp.thecloud.so/mcp

Steps

Add the server Run this once. Gemini CLI stores the server and opens your browser to sign in to The Cloud.
```
gemini mcp add --transport http the-cloud https://mcp.thecloud.so/mcp
```
Confirm it registered Run gemini mcp list and check that the-cloud is listed and connected before you start a session.

Verify it worked

Start a new chat and send one word: sync. The Cloud answers with its Charter, your memory, and a line confirming the sync. If you get that back, the connection is live and every other tool is available to that chat.

Troubleshooting

The command is not recognised. Your Gemini CLI predates mcp add. Update the CLI. There is no JSON fallback we document for Gemini, because the CLI owns its own config format.
The browser never opened. You are on a headless box. Run the command on a machine with a browser, or use a static Bearer key from a client that can send headers.
The tool list looks stale. Reconnect the server, or restart Gemini CLI, so it re-reads tools/list. The Cloud adds tools often and a client caches the list from its last handshake.
Gmail or Calendar shows an "unverified app" warning. Google verification for The Cloud is still in review. You can continue past the warning, or skip the Email and Calendar tools. Every other tool works either way.

Connect into The Cloud for auth, every other client, and the full tool surface.
Tool reference for every tool and its safety class.
Safety and consent for what your AI can do without asking, and what it cannot.
Build on The Cloud to ship a hosted Studio app from the client you just connected.

Troubleshooting

The command is not recognised. Your Gemini CLI predates mcp add. Update the CLI. There is no JSON fallback we document for Gemini, because the CLI owns its own config format.

The browser never opened. You are on a headless box. Run the command on a machine with a browser, or use a static Bearer key from a client that can send headers.

The tool list looks stale. Reconnect the server, or restart Gemini CLI, so it re-reads tools/list. The Cloud adds tools often and a client caches the list from its last handshake.

Gmail or Calendar shows an "unverified app" warning. Google verification for The Cloud is still in review. You can continue past the warning, or skip the Email and Calendar tools. Every other tool works either way.

Connect Gemini CLI