Connect Claude Code

Connect Claude Code

Claude Code connects in one terminal command. It drives the browser sign-in for you, so there is no JSON file to edit and no key to paste. After that, Claude Code reads your Memory and works in your workspace from any project 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.
• Claude Code installed, and a terminal where claude 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

1. Add the server Run this once. Claude Code registers the server and opens your browser to sign in to The Cloud.

   claude mcp add --transport http the-cloud https://mcp.thecloud.so/mcp

2. Load your memory in a session In a Claude Code session, type /cloud to load your Cloud memory into that session before you start working. Sending sync does the same thing through the tool itself.
3. Decide what prompts you (optional) By default Claude Code asks before every tool call. Add this to ~/.claude/settings.json so everyday reads and writes run without a prompt while deletes and sending email still stop and ask. The ask rules win over the broad allow.

   {
     "permissions": {
       "allow": ["mcp__the-cloud"],
       "ask": [
         "mcp__the-cloud__deleteTodo",
         "mcp__the-cloud__deletePage",
         "mcp__the-cloud__deleteFolder",
         "mcp__the-cloud__deleteFile",
         "mcp__the-cloud__deleteEvent",
         "mcp__the-cloud__deleteDraft",
         "mcp__the-cloud__deleteLabel",
         "mcp__the-cloud__trashEmail",
         "mcp__the-cloud__sendEmail"
       ]
     }
   }

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.

• Then try a real one: "Draft a one page brief for the Q3 roadmap and put it in my Work space." You get back a link to the Page it created.

Troubleshooting

• The command reports the server already exists. Remove it with claude mcp remove the-cloud and run the add command again.
• The tool list looks stale. Reconnect the server, or restart Claude Code, 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.
• You need a static key for CI. The browser flow is not available in a headless run. Generate a key in the workspace under Settings, in the AI tab, and send it as a Bearer header. The header form is on Connect into The Cloud.

Next

• 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.