--- title: "Basic Memory Cloud" description: "Cloud remote MCP setup, web editor, CLI tools, and snapshots for Basic Memory Cloud." canonical_url: "https://docs.basicmemory.com/cloud/cloud-guide" --- # Basic Memory Cloud > Cloud remote MCP setup, web editor, CLI tools, and snapshots for Basic Memory Cloud. Basic Memory Cloud provides hosted MCP access with no local installation required. Bring your knowledge to the cloud - all your existing notes, connections, and context accessible from anywhere. **Why use Basic Memory Cloud?** - Access from any device - Easily import your data - 2-minute setup - Local sync optional - OAuth authentication --- ## Setup with Claude Open the [Claude Directory](https://claude.ai/directory), search for **Basic Memory Cloud**, and select **Install**. Complete the Basic Memory authorization flow, then ask Claude to list your Basic Memory projects. The published remote connector works across Claude web, desktop, mobile, Cowork, and Claude Code. For the directory walkthrough and manual custom-connector fallback, see the [Claude Desktop Integration](https://docs.basicmemory.com/integrations/claude-desktop) guide. --- ## Setup with ChatGPT Open [Basic Memory Cloud in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6a49590bf6348191a16c0b87ca6b01b4), select **Connect**, and complete the Basic Memory authorization flow. Select **Try in chat** to start a conversation with the app enabled. For the full Plugin-directory walkthrough, managed-workspace notes, and manual custom MCP fallback, see the [ChatGPT Integration](https://docs.basicmemory.com/integrations/chatgpt) guide. For clients or advanced setups that require a server URL, the Basic Memory Cloud remote MCP endpoint remains: ```text https://cloud.basicmemory.com/mcp ``` --- ## Web App Browse, edit, and collaborate on your cloud notes directly in your browser at [app.basicmemory.com](https://app.basicmemory.com). **Key features:** - **Edit notes** - A rich editor, plain Markdown source mode, and a read-only preview with clickable wiki links - **Review changes** - Attributed comments and insertion, deletion, or replacement suggestions using portable CriticMarkup - **Wiki** - Open any project as pages, with an overview, folder pages, and a change log kept current - **Live notes** - Charts, boards, and live query views written as Comark components in Markdown - **Agents** (beta) - Agents that look after your notes, with every change in a review queue - **Usage** - Where every credit went, and a spending limit you set - **Import data** - Bring in project ZIPs, Claude or ChatGPT exports, or memory-json from **Settings → Import** - **Manage projects** - Create, switch between, and manage projects - **Upload folders as ZIP** - Zip a folder and import it into any writable project — no CLI needed - **Download archives** - Export projects as zip files for backup For the complete web app guide including editing modes, drafts, AI collaboration, importing, and project management, see the [Web App Guide](https://docs.basicmemory.com/cloud/web-app). Compatible MCP clients can also open a focused Basic Memory workspace inside the conversation for browsing, search, graph exploration, editing, and review. See [Pocketbook](https://docs.basicmemory.com/cloud/mcp-app). --- ## Command Line Tools The CLI tools are **optional** but enable advanced features like project management, file upload, and local file sync. **Requirements**: an up-to-date Basic Memory CLI (`bm update`). See [Local Installation](https://docs.basicmemory.com/local/local-install) for installation. **Why use the CLI?** - Manage multiple projects from terminal - Upload entire folders to cloud - Sync local files with push and pull - Automate workflows with scripts ### Quick Start ```bash # Authenticate — OAuth in the browser, validates your subscription bm cloud login # Check the connection: cloud host, API key status, OAuth token status bm cloud status # List projects across your workspaces bm project list # Create a cloud project (--cloud is required; add --default to make it the default) bm project add my-new-project --cloud ``` `bm cloud login` authenticates the CLI — it does **not** change project routing or start syncing files. Projects stay local unless you route them through cloud with `bm project set-cloud `; revert with `bm project set-local --local-path `. See [Local & Cloud Routing](https://docs.basicmemory.com/cloud/routing) for the full routing model. If you log in without an active subscription, you'll see **"Active subscription required"** — subscribe at [basicmemory.com/subscribe](https://basicmemory.com/subscribe?utm_source=docs&utm_medium=docs&utm_campaign=cloud-guide). `bm cloud logout` removes your OAuth tokens. A saved API key is **not** removed — it keeps working for cloud-routed projects, so delete it separately if you need to revoke access. The full command walkthrough — sign-in options, API keys, workspaces, routing, sync, and snapshots — lives on the [Cloud CLI](https://docs.basicmemory.com/cloud/cloud-cli) page. --- ## Remove a Cloud Project and Its Data Removing a cloud project **always deletes its files from cloud storage** — there is no option to keep them under a deleted project. The CLI warns you first and asks for confirmation: Deleted cloud files can be recovered only from a cloud snapshot. Run `bm cloud snapshot list` to check what you have before removing a project, and see [Cloud Snapshots](https://docs.basicmemory.com/cloud/cloud-snapshots) for restore steps. Changed in v0.24 — see [Upgrading to v0.24](https://docs.basicmemory.com/whats-new/v0-24-upgrade). ```bash # Remove the project and delete its cloud files (asks for confirmation) bm project remove research --cloud # Skip the prompt in scripts bm project remove research --cloud --yes # Also delete this machine's local sync directory bm project remove research --cloud --delete-local-files ``` A configured local sync directory is **kept** unless you pass `--delete-local-files`. (Before v0.24, `--delete-notes` deleted the local sync directory as a side effect; on cloud projects it no longer does, and `--delete-notes` now applies only to local projects.) A cloud-only project removed without `--cloud` is still treated as cloud-routed. Removing a cloud project also drops its local routing entry, so the name can be added again. Hosted deletion is asynchronous: the project is hidden from cloud workspace operations when deletion is accepted, then a background job removes its database rows and every object under the project's storage prefix. The MCP `bm_project_delete` tool on a cloud route also always deletes the project's cloud files. From a local stdio MCP session, pass `workspace` to route the request to that cloud workspace. Its `delete_notes` parameter applies only to local projects. MCP deletion never removes a local sync directory; use `bm project remove --delete-local-files` when you want both copies gone. The MCP response reports the pending deletion status and background job ID. --- ## Upload Files to Cloud **No CLI needed for one-off uploads.** In the web app, **Settings → Import → Project ZIP** imports a zipped folder into any writable project — pick the team and target project, optionally a destination folder, and upload (ZIPs up to 100MB; markdown files are indexed automatically). The **Activity** view tracks the job after it starts. For scripted or repeated uploads, use `bm cloud upload` from the CLI: ```bash # Upload a directory to existing project bm cloud upload ~/my-notes --project research # Upload a single file bm cloud upload important-doc.md --project research # Upload and create project in one step bm cloud upload ~/local-project --project new-research --create-project # Upload without indexing afterward bm cloud upload ~/bulk-data --project archives --no-index ``` **File Filtering:** The upload command respects `.bmignore` and `.gitignore` patterns, automatically excluding: - Hidden files (`.git`, `.DS_Store`) - Build artifacts (`node_modules`, `__pycache__`) - Database files (`*.db`, `*.db-wal`) - Environment files (`.env`) **Complete Example:** ```bash # 1. Login to cloud bm cloud login # 2. Upload local project (creates project if needed) bm cloud upload ~/specs --project specs --create-project # 3. Verify upload bm project list ``` After sync completes, the notes are available in the [web app](https://app.basicmemory.com) and for AI conversations. To edit both locally and in cloud, sync with push/pull — see the [Cloud Sync Guide](https://docs.basicmemory.com/cloud/cloud-sync). --- ## Cloud Snapshots Basic Memory Cloud includes point-in-time snapshots for backup and recovery. Create manual snapshots before major changes, or rely on automatic daily backups. **Key features:** - Create unlimited manual snapshots - Automatic daily snapshots - Browse historical versions - Restore individual files or folders ```bash # Create a snapshot before major changes bm cloud snapshot create "Before reorganization" # List all snapshots bm cloud snapshot list # Browse snapshot contents bm cloud snapshot browse snap_abc123 --prefix notes/ # Restore a file from a snapshot bm cloud restore notes/example.md --snapshot snap_abc123 ``` For complete snapshot management including restore procedures and best practices, see the [Cloud Snapshots Guide](https://docs.basicmemory.com/cloud/cloud-snapshots). --- ## Migrating to Cloud Already using Basic Memory locally? You have two options: ### Option 1: One-Time Upload (Fastest) Upload your existing local project to cloud: ```bash # Login first bm cloud login # Upload entire project bm cloud upload ~/basic-memory --project main --create-project ``` Prefer the browser? Zip your `~/basic-memory` folder and import it via **Settings → Import → Project ZIP** — no CLI required. **Use when:** - You want to move to cloud-only - One-time migration is sufficient - Don't need ongoing local-cloud sync ### Option 2: Local File Sync (Hybrid Workflow) Set up sync to work both locally and in cloud: ```bash # Login and setup sync bm cloud login bm cloud setup # Add your existing project as a cloud project with a local sync path bm project add main --cloud --local-path ~/basic-memory # First push (preview, then upload your local files) bm cloud push --name main --dry-run bm cloud push --name main # Ongoing: pull cloud changes down, push local changes up bm cloud pull --name main bm cloud push --name main ``` **Use when:** - You want to edit both locally (Obsidian, VS Code) and in cloud - Need offline access - Want changes to flow both ways `pull` and `push` are the supported sync workflow on Personal and Team workspaces. The older `bm cloud sync` and `bm cloud bisync` mirror commands are deprecated as of v0.24. Both methods preserve all your notes, relations, and tags. Choose based on whether you want cloud-only or hybrid local+cloud workflow. See the [Cloud Sync Guide](https://docs.basicmemory.com/cloud/cloud-sync) for detailed sync configuration. ### Moving between cloud workspaces If your notes already live in one cloud workspace (say, your personal one) and you want to bring them into a [team workspace](https://docs.basicmemory.com/teams/about) — or vice versa — see [Copy Content Between Workspaces](https://docs.basicmemory.com/teams/copy-between-workspaces) for the project ZIP, single-note, MCP, and local-sync recipes. --- ## Next Steps Run some projects locally and others in the cloud. Sync local files with push and pull. Complete CLI command reference. All available MCP tools for AI assistants. ## Sitemap See the full [sitemap](https://docs.basicmemory.com/sitemap.md) for all pages.