Second Brain Cloudflare is not another notes app.

It is closer to a private memory service for AI tools: Claude, Cursor, Codex, ChatGPT, Gemini CLI, browser capture, Obsidian, calendars, email imports, and other MCP-compatible clients can all write to and recall the same memory layer.

The interesting part is the deployment model:

Cloudflare Workers + D1 + Vectorize + Workers AI + KV + static dashboard

So this belongs in the same Cloudflare-serverless family as Memos Worker, Inkstone, Cloudflarebase, and the broader Workers/D1/KV/R2 architecture note.

But the product shape is different.

Second Brain Cloudflare is built around memory retrieval, not document editing.

What It Does

The core workflow is simple:

  1. Capture something you want your AI tools to remember.
  2. Store it in your own Cloudflare account.
  3. Embed it semantically.
  4. Retrieve it later through MCP, REST, the dashboard, CLI hooks, or connected integrations.

The repository exposes tools such as:

  • remember;
  • append;
  • update;
  • recall;
  • brief;
  • resolve;
  • digest;
  • history;
  • list_recent;
  • get;
  • forget;
  • undo;
  • link;
  • unlink;
  • connections;
  • share;
  • prompt capsule helpers.

That gives it a more operational feel than a notebook. You do not just open a page and write. You teach a shared memory layer facts, decisions, preferences, project context, historical changes, and team notes that agents can recall later.

Architecture

The repo is a TypeScript Cloudflare Worker application.

Layer Second Brain Cloudflare Uses
Runtime Cloudflare Workers
App data D1
Semantic index Vectorize
Embeddings Workers AI, @cf/baai/bge-small-en-v1.5
Reranking Workers AI, @cf/baai/bge-reranker-base
Digest and insight reasoning Workers AI LLM bindings
OAuth/cache/state KV
Dashboard Static assets served by the Worker
Agent protocol MCP plus REST
Scheduled work Cloudflare Cron Triggers

The default embedding dimension is 384, matching the BGE small embedding model. The Vectorize metric is cosine.

That is why it is materially different from many small note apps: semantic search is a first-class storage path, not a later add-on.

What Gets Stored Where

Second Brain Cloudflare does not store your notes as Markdown files.

The main content lives in D1 tables. The schema includes entries, tags, sources, validity metadata, workspaces, users, memberships, projects, graph edges, events, maintenance cursors, and prompt capsule revisions.

Vectors are written separately to Vectorize. The capture pipeline chunks content, embeds the chunks, and stores vector metadata that points back to the D1 entry.

In practical terms:

Data Storage
Memory text and metadata D1
Teams, users, projects, events D1
Graph links between memories D1
Full-text search index D1 FTS / fallback SQL
Embedding vectors Vectorize
OAuth/runtime cache/capsule cache KV
Dashboard files Worker static assets

That makes it very good for AI recall, but it is not the same ownership model as a Git-backed Markdown vault.

Search and Recall

Recall combines several paths:

  • semantic vector search through Vectorize;
  • keyword search through D1 full-text search;
  • graph expansion through linked memories;
  • reranking;
  • temporal filtering with as_of;
  • workspace/project/source/tag filters.

The keyword side matters more than it sounds. Exact names, ticket IDs, versions, domains, and foreign-language phrases are often better found with full-text search than embeddings.

The vector side handles the more AI-native query:

What did we decide about the Cloudflare memory project?

Even if the captured memory did not use those exact words, the semantic index can still surface it.

Local Test

The repository includes a local UX harness:

npm run dev:local

In my test I ran it at:

http://localhost:8788/

The dashboard served successfully, the PWA manifest loaded, and the test token was:

ux-harness-local-token

Because the harness listens on port 8788, it was also reachable from the LAN machine address:

http://192.168.1.2:8788/

The dashboard accepted the bearer token properly through the connect form.

I then captured a memory:

curl -X POST http://127.0.0.1:8788/capture \
  -H "Authorization: Bearer ux-harness-local-token" \
  -H "Content-Type: application/json" \
  -d '{"content":"Foss Engineer test memory: Second Brain Cloudflare stores semantic memories for AI tools and recalls them through MCP.","source":"foss-test","tags":["foss","cloudflare"]}'

The API returned ok: true.

Then recall worked:

curl "http://127.0.0.1:8788/recall?query=semantic%20memories%20AI%20tools&topK=3" \
  -H "Authorization: Bearer ux-harness-local-token"

The result returned the inserted memory with:

{
  "semantic_unavailable": false
}

So the local harness is useful for development validation. It is not the same as a production homelab Docker deployment.

Deployment

There are two realistic deployment paths.

Desktop Installer

The desktop installer is the friendliest path.

It provisions the required Cloudflare resources in your account and stores the generated auth token in your OS keychain. The installer is designed to avoid forcing normal users through Wrangler, Node, Git, and manual Cloudflare binding setup.

This is still your Cloudflare deployment. The desktop app is not a hosted SaaS that owns your memories.

Manual Wrangler Deployment

The manual path is closer to:

npm install
npm run vectors:create
npm run deploy

Then set the Worker secret:

wrangler secret put AUTH_TOKEN

The deployed MCP endpoint is:

https://YOUR-WORKER-URL/mcp

Clients should authenticate with:

Authorization: Bearer YOUR-TOKEN

Query-string token auth was intentionally removed because URLs leak into browser history, reverse-proxy logs, screenshots, and telemetry.

How It Compares

Project Best Fit
EdgeEver Full Evernote-style knowledge base with rich editor, Docker mode, Cloudflare mode, attachments, PWA, and MCP
Memos Worker Lightweight Cloudflare-native memo app
Inkstone Cloudflare-native Markdown notebook
FlareMo Memos-style Cloudflare knowledge base with team/AI ideas
Cloudflarebase Backend platform on Cloudflare, not a note or memory app
Second Brain Cloudflare MCP-first semantic memory layer for AI tools

The closest comparison is not “Evernote alternative”.

It is “private memory server for all my AI agents”.

FAQ