Unabyss
MCP-native self-updating context layer for your AI
1.9K followers
MCP-native self-updating context layer for your AI
1.9K followers
Set it up once and never re-explain yourself to AI again. Connect the apps you use daily - Unabyss will extract, structure, and update your context automatically. Share it with any AI tool via MCP, with granular control over what each tool can see.
This is the 2nd launch from Unabyss. View more
Unabyss for Claude
Launching today
Claude doesn't know what happens in GPT. Neither one really knows who you are or what your company does. Now they can.
Unabyss gives Claude memories from your other AI agents and everyday apps: email, Drive, GitHub, Notion, meeting recorders, and 20+ more. It saves new memories too, so GPT and Cursor stay in sync with the exact same context - sharper than wiring each tool into Claude one by one.
Finally, a real memory that follows you. Private. Portable.
Free Options
Launch Team / Built With
Unabyss
Hey PH 👋 Philip here, co-founder of Unabyss.
Our first launch, back in May, ended up winning #1 product of the day - still can't quite believe that one. Thank you!
Since then, we listened to your feedback & rebuilt the whole thing around one idea: your context should live where you actually work. So we moved Unabyss into Claude.
What's new since May - and why we're relaunching:
Claude-first, MCP-first. No browser needed anymore. Connect the MCP once, and everything happens inside Claude.
The part we're most excited about: save context from any Claude chat into Unabyss - and reuse it in Cursor, GPT, or any other agent. What you work out in one place carries over everywhere. Memory that follows you, instead of resetting every session.
Rebuilt the MCP from scratch, now loaded with 60+ skills - Claude just works with your context. No setup, no copying files between tools.
15+ new integrations along the way: Obsidian, HubSpot, Notion, Asana, GitLab, and more.
Who it's for: builders wiring up AI tools, founders juggling context across a dozen apps, consultants who live in other people's stacks. Anyone tired of re-briefing their AI every morning.
Last time, we shipped a context layer you configured in an app. This is context that lives in Claude and travels with you.
We're around all day - try it at unabyss.com and tell us how you'd use portable memory, and what's missing. Tear it apart!
Yours,
Philip & the Unabyss team
I live in Claude Code all day and maintain CLAUDE.md files across client projects, so the line about a context file being frozen the moment you write it hit home. Mine rot quietly until something breaks. Spent a while on your landing and FAQ before commenting, the comparison against built-in memory and plain context files is the clearest pitch I have seen for this category, and tagging by topic, sensitivity and source is the part that actually matters.
Two honest questions before I plug it into client work. First, when a wrong fact gets extracted from an old Slack thread, where do I see and fix it before it follows me into every tool? A reviewable, editable memory list would be the make or break feature for me. Second, for the agency use case, how confident are the sensitivity tags in practice? One client detail leaking into another client's session over MCP would end the experiment instantly.
Upvoted, and the Pro plan pricing next to a Claude Max subscription is smartly placed.
Unabyss
@abdullah_javaid3 appreciate your feedback!
1. Wrong facts -> we have conflict resolution in place, so incorrect information won't be retrieved from memory. Facts are cross-checked against other, more recent memories before they're retrieved.
2. Source tagging is bulletproof. Permissions for sensitive/confidential data are handled by the agent, so I can imagine edge cases where things don't work exactly as intended. Agency use-case is very specific and we're launching the agency context architecture soon. Memory silos will be fully isolated, making this 100% secure. Until then, I'd recommend using source-level (connection-level) permissions.
Happy to update you when 2) is live!
Shared memory sounds simple until two apps write conflicting facts about the same user and the model has to reconcile them. How are you handling write conflicts and stale context across sources? That is where most memory layers break down under real usage. Good problem to be working on.
Unabyss
@shivangit26 totally agree! Unabyss executes conflict resolution just before retrieval, so any potentially incorrect fact is checked against other memories, with recency taken into account. Outdated or incorrect information are simply filtered out before being returned.
And btw this is a core part of our memory architecture, and we're improving it every day. Literally!
When local version? I need to start pushing this to my clients.
Unabyss
@greenparrotnow we're shipping local memory next week. I'll share closed beta with you via DM!
How do you ensure that Claude & ChatGPT have the same memory? And does it work for OpenClaw too?
Unabyss
@amanda_baldwin1
Everything happens via our "store" tool in memory. You can save every conversation to Unabyss - just call it manually (e.g. "save it to Unabyss") or adjust your e.g. Claude preferences so that every chat is saved to your memory.
Some users choose the 1st option, some the latter - depending on how much information they want to transfer to Unabyss.
And yes, it works for OpenClaw too! In general, it works with every AI tool that has MCP :)
Voquill
Nice idea. Congratulations!
How easy is it to clean up or remove memories if something gets saved by mistake?
Unabyss
@henry_habib extremely easy :)
if something gets saved by mistake, you can ask Unabyss to edit/remove it wherever you use it (Claude, GPT, Cursor, or in Unabyss itself :))
and you want to know what Unabyss knows about specific topic - you can talk it through. And (on Monday) we'll release Context View, where you'll see every information that Unabyss has!
Are you introducing team plans?
Unabyss
@jakub_witowski yes, next week. I'll let you know as soon as it's ready! But you can already onboard your team and we'll merge your accounts into one org in a few days.