Give Claude memory
of what you save.
Built-in memory only remembers what Claude has been told. ContextBolt gives Claude access to your real saved content, every tweet, post, and link, searchable by meaning from any conversation.
The problem
Why this is harder than it should be
Claude.ai's memory captures conversations. Useful for preferences. Useless for the article you saved last Tuesday. Your saved bookmarks, threads, and posts live somewhere else, and Claude has no way in. So every conversation starts from scratch, with you pasting links one at a time.
How ContextBolt does it
Three steps. All automatic.
Install for Chrome (one click)
Add the free ContextBolt extension. Bookmarks from X, Reddit, and LinkedIn are captured, indexed, and AI-tagged in the background.
Connect via MCP (Pro)
Pro users get a personal MCP endpoint. One JSON block in your Claude Desktop or Claude Code config and the connection is live.
Ask Claude what you saved
'What did I bookmark about pricing?' or 'Find that thread on hiring.' Claude searches your real library and answers with what is actually there.
MCP integration
Searchable from inside your AI agent
Pro users get a personal MCP endpoint. One line of config and Claude, Cursor, or Windsurf can search your bookmarks during a conversation.
Plug into the AI tools you already use
Any MCP-compatible client works. See all integrations →
Why ContextBolt
Built for retrieval, not just storage
Real memory, not just chat history
Built-in memory remembers what Claude was told. ContextBolt remembers what you saved. Every bookmark, thread, and post is searchable from any conversation.
One library, all your AIs
Same MCP endpoint works in Claude Desktop, Claude Code, Cursor, Windsurf, and Cline. Move between tools, your memory comes with you.
You own the memory
Bookmarks are stored in your account, end-to-end encrypted in cloud sync. Revoke the MCP token any time. Cancel any time. The library exports cleanly.
Read more
Want every workaround compared?
The blog post below covers every method, every limit, every workaround. The page you are on now is the install.
FAQ
Common questions
Does Claude already have long-term memory?
Yes, Claude.ai launched built-in memory free for all users on 2 March 2026. It synthesises facts from your conversations and surfaces them in future chats. It does not include anything outside Claude though, so the article you bookmarked yesterday is still invisible to it. ContextBolt's MCP endpoint covers that gap.
What is the difference between built-in memory and MCP memory?
Built-in memory is inward. It remembers what you told Claude in past conversations. MCP memory is outward. It connects Claude to external data in real time. Built-in for preferences, MCP for content. Both are useful for different jobs and they happily run side by side.
Do I need to be a developer to set this up?
No. Setup is one JSON snippet pasted into a config file, then a client restart. The dashboard gives you copy-paste snippets for Claude Desktop, Claude Code, Cursor, Windsurf, and Cline. Five minutes from install to first query.
Is this free?
The Chrome extension and local capture are free, with up to 150 bookmarks indexed on the free tier. The MCP endpoint is a Pro feature at GBP 4 per month, and includes unlimited bookmarks, encrypted cloud sync, and the personal endpoint URL.
How is this different from RAG or vector databases?
RAG and vector DBs are infrastructure you have to build. ContextBolt is the same idea wrapped as a product. Bookmarks become embeddings automatically, search runs on a managed vector index, and the result is exposed as an MCP server. You skip the build and just point Claude at the URL.
Can Claude write or delete bookmarks?
No. The MCP endpoint is read-only. Claude can search and quote your bookmarks but never modify them. The token is rotatable and revocable from the dashboard at any time.