Launched this week
Unabyss
MCP-native self-updating context layer for your AI
1.6K followers
MCP-native self-updating context layer for your AI
1.6K 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.
Do you plan to be HIPAA and SOC 2 compliant in the future? I work in health tech and would love to use this, but we have high security standards we have to meet for new tools.
Unabyss
@toni_toomey1 Yes! SOC 2 is on our roadmap very soon, but HIPAA is probably a bit of a long term :/
I'm curious about the "automatically extract and structure" feature. Are you testing it on dirty/chaotic data or only on clean data? Because my brain is 80% organized chaos.🌬️
Unabyss
@olivier_jury Unabyss works well with structured data like Obsidian and Notion notes, but also with messy ones ;). In our engine, all contextually related data is grouped and tagged, so your chaos is automatically tidied up.
Unabyss
@olivier_jury there is no limit on data stored or imported so go on!
Unabyss
@olivier_jury Just connect Notion to your Unabyss account. In the connection step, you can either import everything or select the pages you want to sync. And as a test, you can select those 20 ;) no need for manual export and import.
Unabyss
@olivier_jury one of our biggest advantages is independence - data always stays yours and you can use it wherever you want. In Claude, Cursor, ChatGPT, OpenClaw - it's up to you. And context always stays up to date. We strongly doubt that big labs will allow their users to switch easily to other providers ;).
But yes, we also want to constantly advance our extraction, segmentation, and retrieval engines.
@dominik_bartosik Ok compris pour l’indépendance. Du coup sur la qualité brute : vous avez des benchmarks internes vs les Projects/Spaces natifs de Claude, Notion, Perplexity ?
> Même si vous êtes portables, si le contexte est 20% moins bon, la plupart des gens resteront dans l’écosystème d’origine.
Loving the core idea - context portability is a real problem...
What I'd hesitate with is trust tho... once users connect Gmail, Slack, GitHub, etc, adoption becomes less about capability and more about confidence.
What have you found is the biggest trust barrier so far?
Unabyss
@kastelicjakob it is a barrier that's true. But we have a few safeguards in place to reassure users that it is safe to connect their accounts to Unabyss.
1. We are only reading the data - no sending emails via Gmail, no editing Notion pages.
2. You can precisely see in the Sources page what data we synced.
3. At any time, you can permanently delete all data, picked app sources, or the whole account.
Data is always yours - and always will be.
This is the problem I keep solving badly with a CLAUDE.md I copy into every tool, so MCP-native is what makes it click. One security question: when you extract context from Gmail and Slack, does it store abstracted summaries, or can verbatim snippets like client names and confidential bits land in the files? Granular per-tool sharing only helps if the extraction upstream isn't pulling sensitive content into them to begin with.
Unabyss
@adrian_rebega depending on the source, we are storing both abstract summaries and snippets, where are all the details. But they live in the memory itself, not it easy to access raw data form. For each agent connected to the Unabyss MCP, you can set a permission level that defines what agents can access. We have checkpoints on what Unabyss returns to the agent to make sure nothing the user doesn't want to share is included.
Unabyss is extremely precise in understanding your digital life - that is only possible when he get's your full digital representation.
How does it know what to send to which app? Like, if I connect email assistant and my coding assistant with MCP, are they getting the same stuff?
Unabyss
@marcin_szatkowski they will get what they ask for via MCP. they both have access to the same vault, but can get completely different parts of it, depending on what they ask for. to your example - such two tools will need completely different things, so they will get information adjusted to their needs.
GrowMeOrganic
How exactly is the context connected to tools? Is it MCP only?
Unabyss
@iamanantgupta currently you can connect your Unabyss context to the agents like Claude, ChatGPT, Cursor, OpenClaw etc. via MCP. But apps like Gmail and Notion, you connected to Unabyss via simple and secure OAuth. I hope this answered your question ;).
Will it support my open claw ? Also I use 3 subscription of claude for different purposes. Is it possible to select what is bbeing shared via unabys?
Unabyss
Hi @greenparrotnow! All the agents you mentioned can pull your context via MCP - claude and openclaw. And even if you have multi-accounts. Also, both of them work especially well with Unabyss when you add an optional system prompt. Look in our guide: https://app.unabyss.com/mcp/guides.