Jason Peterson A few weeks ago I wrote about building a second brain as a remote MCP server on Cloudflare Workers. Quick update: it’s working really well.
It got useful fast
The cold start problem I worried about turned out to be easy to solve. The Anthropic Gmail MCP made it simple to surface old conversations, contacts from years ago, events I’d half-forgotten. I ran targeted Gmail searches and let Claude extract entities and relationships from the results. Within a few sessions the graph had depth. People, companies, projects, timelines, all connected.
Now I use it for things as simple as pulling up a relative’s phone number. Or as involved as searching my professional network for someone with specific expertise. It handles both because the primitive is flexible enough to store anything.
The Cloudflare Workers layer has been solid
No downtime, no cold starts that I’ve noticed, no surprises. The free tier has been sufficient for my usage so far. Vectorize handles the semantic search without breaking a sweat. D1 just works. I haven’t had to think about infrastructure at all, which is the whole point of serverless.
Remote MCPs for work
I also added a couple of remote MCPs that I use for work to the same Cloudflare setup. Having those accessible from every Claude surface, not just my laptop, has been a real quality of life improvement. The pattern of deploying MCP servers as Cloudflare Workers and registering them as remote connectors is something I’ll keep using.
What I’ve learned
The biggest thing: just tell it to remember. That’s it. “Remember that Sarah prefers email.” “Remember that the deadline moved to April 15.” Claude figures out where it goes in the graph. I don’t think about entities or relations. I just talk, and the structure takes care of itself.
It’s become one of my most-used tools across the whole Anthropic ecosystem. Phone, laptop, browser, terminal. Same memory everywhere.