The CloudThe Cloud
  • Tools
  • Case studies
  • Pricing
Sign inSign up
Start for free
The CloudThe Cloud

Your Life WorkSpace

© 2026 The Cloud. All rights reserved.

Connect an AI to The Cloud

The Cloud is a VastMemory any AI can read and write — over the Model Context Protocol (MCP). Point your assistant at the endpoint below and it can use The Cloud as durable, shared memory: pages, tasks, calendar, and more. No insider setup required.

The MCP endpoint

One HTTP endpoint, JSON-RPC 2.0. This is the only address you need:

https://mcp.thecloud.so/mcp

Connect — no API key

One step per client. Your browser opens once to sign in to your Cloud account, and the connection is live. No secret is copied, pasted, transcribed, or stored anywhere.

Claude Code (CLI)

One terminal command. Claude Code drives the browser sign-in.

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

Cursor

One-click install with the button below, or paste the config into mcp.json + Reload Window. First connection opens the browser to sign in.

File: ~/.cursor/mcp.json (global) or project .cursor/mcp.json

{
  "mcpServers": {
    "the-cloud": {
      "url": "https://mcp.thecloud.so/mcp"
    }
  }
}

Gemini CLI

One terminal command. Gemini CLI opens your browser to sign in — no JSON file to edit, no API key needed.

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

Claude Desktop

Settings → Connectors → Add custom connector. Paste the endpoint. Sign in when prompted.

https://mcp.thecloud.so/mcp

Static API key — for CI, headless, and unsupported clients

For environments where the browser sign-in isn't available (continuous integration, scripted setups), or clients that don't support MCP's OAuth flow yet (Windsurf, ChatGPT), generate an API key under Settings → AI and pass it as a Bearer header:

{
  "mcpServers": {
    "the-cloud": {
      "type": "http",
      "url": "https://mcp.thecloud.so/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

The in-app setup guide under Settings → AI has the exact snippet for each client, including Windsurf and ChatGPT.

What your AI can do

Once connected, your assistant can read and write your Pages and Memory, manage Tasks and Calendar events, track Habits, and reach your Files and Profile — using The Cloud as the memory it carries between sessions.

The tools, by group

The Cloud exposes the workspace as MCP tools, grouped by what they reach. Read tools return your data; write tools create or change it and hand back a link.

  • Pages

    list spaces, search, read, create, edit, append, move, rename, delete documents

  • Memory

    create, read, search, update, and organize durable memories

  • Tasks

    task lists and to-dos — create, complete, move, update, delete

  • My Day

    read and add to today's daily page and the My Day files

  • Calendar

    list, read, create, update, delete events; find free time

  • Email

    search, read, send, label, draft, and archive Gmail

  • GitHub

    list repositories, issues, and pull requests; create issues; search code

  • Habits, Files & Profiles

    create and log habits; manage folders and files; build public profile pages

Every tool carries a safety annotation — reads, ordinary writes, and destructive actions are each marked, so your client knows what is safe to run and what to confirm first.

Troubleshooting

The connector won't connect

Confirm you pasted the exact endpoint above. Remove the connector and add it again — the browser sign-in runs once more and the session refreshes.

An “unverified app” screen when connecting Gmail or Calendar

Google verification for those scopes is still in progress. Until it finishes you can proceed past the screen, or skip the Email and Calendar tools — every other tool works without them.

An API-key client returns 401 Unauthorized

The key is missing or was revoked. Generate a fresh one under Settings → AI and update the Authorization header in your client's MCP config.

Tools look missing or stale after a change

Reconnect the server, or restart your client, so it re-reads the tool list from a fresh session.

See it work

Once connected, you talk to your AI the way you always do — it reaches The Cloud on its own. A few things to try:

Remember that our launch is May 30 and the directory submission is the priority.

The AI writes the fact into your VastMemory. Every later session that connects The Cloud carries it — you never re-explain.

Draft a one-page brief for the Q3 roadmap and put it in my Work space.

The AI creates the page in The Cloud, writes the brief, and hands back a link you can open or share.

What do I have on tomorrow, and what's still open on the launch?

The AI reads your calendar and tasks and answers from your real data — not a guess.

The Charter

On connecting, a connected AI pins The Cloud's Charter — the master document that keeps it guided, governed, and in sync with your memory for the whole session. Sharing and visibility always stay under your control: an AI never makes anything public on its own.