Second Brain Cloudflare icon

Second Brain Cloudflare

Second Brain Cloudflare is a self-hosted memory layer for AI tools, designed to store notes, decisions, and project context once and recall them across connected clients. It runs on Cloudflare and supports semantic retrieval plus multiple capture paths.

Second Brain Cloudflare

Self-hosted memory for AI clients

Second Brain Cloudflare is a self-hosted memory layer for AI tools. It lets you store notes, decisions, project context, and other snippets once, then retrieve them later from connected clients such as Claude, ChatGPT, Cursor, and other MCP-compatible tools. The project is built to keep your memory in your own Cloudflare account rather than inside a single AI app.

The system centers on semantic recall instead of exact-match search. That means you can ask for information using different wording than you used when saving it, and the service can still surface the relevant memory. The repository also documents ways to capture information from the terminal, Obsidian, iOS Shortcuts, a browser extension, a bookmarklet, and direct AI client commands.

Core capabilities

Memory operations

Save a memory, append to an existing entry, replace an entry entirely, recall by meaning, list recent items, or delete an entry. The API is built around a small set of actions instead of a large interface surface.

Meaning-based recall

Use semantic search so retrieval depends on meaning rather than exact wording. The documentation gives an example where a question about a pricing decision finds the right note even if the original phrasing differs.

Cross-client access

Connect through MCP so AI clients can read and write the same memory layer. The README specifically mentions Claude, ChatGPT, Cursor, Claude Code, and Codex CLI.

Multi-source capture

Capture context from multiple input surfaces, including the terminal, Obsidian, iOS Shortcuts, a browser extension, and a bookmarklet. This makes it easier to save information where it first appears.

Cloudflare deployment flow

Deploy to Cloudflare with automated provisioning for the database, vector index, and Worker. The setup guide says the database schema auto-creates on the first request, reducing manual setup steps.

OAuth and token auth

Support OAuth 2.0 for browser-based MCP clients, with a fallback bearer-token flow for tools that cannot open a browser. The README notes that OAuth requires a KV namespace and is provisioned automatically by the one-click deploy.

Common use cases

  • Cross-tool context continuity

    Keep project decisions, preferences, and working notes in one place so they can follow you between ChatGPT, Claude, Cursor, and other clients.

  • Capture context at the point of discovery

    Save a thought once from the terminal, a browser page, an Obsidian note, or an iOS Shortcut, then retrieve it later without retyping it into each app.

  • Semantic recall for past decisions

    Query memories by intent instead of exact phrasing when you need to find an earlier decision, reference, or note with different wording.

  • Self-hosted personal memory

    Run the system on your own Cloudflare account when you want to keep the memory layer under your control and avoid relying on a single AI vendor's built-in memory.

Pros and Cons

Pros

  • Supports multiple AI clients from a single shared memory layer.
  • Uses semantic retrieval, which is helpful when the saved wording and the later question differ.
  • Offers several capture paths, making it easier to save context from the place it first appears.
  • Can be self-hosted on Cloudflare's free tier at personal scale, with data kept in the user's Cloudflare account.
  • Documents both one-click deployment and manual setup for more control.

Cons

  • Local development has reduced capabilities because Vectorize and Workers AI are only available remotely.
  • Browser-based clients need OAuth setup or token handling, which adds configuration steps compared with a single-app memory feature.

FAQ

Which AI tools can it connect to?

It is designed to connect with Claude, ChatGPT, Cursor, and other MCP-capable clients. The README also lists support paths for Claude Code and Codex CLI, plus manual setup for ChatGPT and Claude desktop or web through a custom MCP connector.

How is it deployed?

The recommended path is the one-click Cloudflare deployment. Cloudflare provisions a D1 database and Vectorize index, prompts for an AUTH_TOKEN, and deploys the Worker automatically. Manual setup is also documented for users who want to run it from a local clone.

What capture and access methods are available?

The source lists a browser-based dashboard, a mobile interface, an Obsidian community plugin, a browser extension, iOS Shortcuts, a bookmarklet, a CLI, and direct AI client access through MCP.

Does it require paid hosting?

The repository states that the system stores memories in your own Cloudflare account and is self-hosted on Cloudflare's free tier at personal scale. The pricing page confirms GitHub hosting for the project itself, but not product pricing beyond the hosting platform used for the codebase.

Are there any local development limitations?

The setup docs note that local development can store entries in D1, but Vectorize and Workers AI are only available remotely. Embedding calls fail gracefully during local development, so semantic recall features may be limited there.

Quick Facts

Category
Developer Tool / AI Memory
Primary use
Shared memory for AI clients
Hosting
Self-hosted on Cloudflare
Deployment
One-click Cloudflare deploy or manual Wrangler setup
Integrations
Claude, ChatGPT, Cursor, Claude Code, Codex CLI, Obsidian, iOS Shortcuts, browser extension
Source domain
github.com