Unabyss
MCP-native self-updating context layer for your AI
2.4K followers
MCP-native self-updating context layer for your AI
2.4K 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
Launched this week
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
I'm a designer, can I use it for multiple clients branding guidelines and other context?
Unabyss
@aleksandra_dabrowska02 yes! you can connect it to our Notion board with the client list, Gmail, and Calendar to get the full context, and then use it in Claude to get whatever you need!
Congrats on your relaunch!! Have you seen more adoption from individual power users or teams?
Unabyss
@tarqiya_forgah Thanks! We have a lot of power users, but interest from teams is strong too. We will be launching team plans next week to accommodate the interest ;)
This new version looks cool. How does permission layer works? Can I give access to my context to someone else?
Unabyss
@karolina_uchacz of course, you can give an access to your context to your brother for example! :))
The MCP-first approach is the right call, and I like that conflicts get flagged to the user instead of the system silently picking one source over another. Most memory tools quietly decide what's true about you, this one at least asks.
One thing I didn't see addressed yet in the thread, when context gets pulled from something like Slack or Gmail that includes other people's names and info alongside yours, is there any filtering to keep that out of your personal vault, or does the extraction just take whatever's in the source as-is.
Congrats on launch number two, Philip. Shared memory across tools is the right problem, re-explaining context to every model is a real tax on anyone working across Claude, Cursor and GPT. The flip side is that a memory layer is also where sensitive data quietly accumulates. I saw the granular per-tool controls in the description, so my question goes one level deeper: is there automatic redaction of sensitive data before a memory gets stored, and can memories expire or be purged by topic? In healthcare, my world, those two features decide whether a tool like this is usable at all.
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.
Unabyss
@jakub_witowski, we are multitasking - as we speak, the team plans are being developed :D.
the onboarding flow for picking which apps to sync feels really thoughtful, especially how you can preview exactly what each AI will see before sharing. nice touch.
Unabyss
@yaar58863951762
Thanks! That's one of the changes we've introduced after feedback from our users - glad to see it improves your experience :)
Unabyss
@yaar58863951762 thanks! feel free to share your feedback anytime ;)