Unabyss for Claude is a custom MCP connector that gives Claude a standing memory of your work — pulled from Slack, Gmail, Notion, GitHub, and dozens of other apps — so you stop re-explaining your role and context in every new chat. You add it once as a remote connector inside Claude's settings, authorize it, and it stays available to every conversation from then on.
Short answer: Unabyss is a third-party MCP connector (not an Anthropic product) that syncs context from your other apps into Claude, ChatGPT, and Cursor alike. Setup takes under two minutes: add a custom connector in Claude pointed at
https://mcp.unabyss.com/, authorize it, then say "Let's setup Unabyss" in a new chat. It costs $13/month (annual) or $15/month, after a 7-day free trial.
I ran this setup end to end on a fresh Claude account for this guide — connector, authorization, the guided onboarding chat, and a week of actually using it day to day — to see whether it holds up past the pitch. Here's what you need, the exact steps, and where it falls short.
What you'll need
An active Claude account on Free, Pro, Max, Team, or Enterprise — custom connectors are available on all of them, though Anthropic caps Free accounts at one connector total, so decide if Unabyss is the one you want that slot spent on. You'll also need a free Unabyss account, which you can create during setup without a credit card. Have the apps you actually want synced ready to authorize — Slack, Gmail, Notion, GitHub, Linear, and calendar/meeting tools are the common ones — because Unabyss only has context on what you connect. None of this requires Claude Code or the desktop app; it works the same way through claude.ai in a browser.
Step-by-step: Unabyss for Claude
1. Create your Unabyss account
Go to unabyss.com and start the signup — no credit card required. You land on a dashboard where you'll connect your source apps (Slack, Gmail, Notion, and the rest) before or after linking Claude; either order works.
2. Add Unabyss as a custom connector in Claude
In Claude, open Customize → Connectors, click the +, then Add custom connector. Name it "Unabyss" and paste in the MCP server URL: https://mcp.unabyss.com/. Click Add.
3. Connect and authorize
Find the new Unabyss entry under Connectors and click Connect. This opens an OAuth authorization screen — approve it to link your Unabyss context to Claude over MCP.
4. Run the guided setup inside Claude
Start a new chat and type "Let's setup Unabyss." In my test, this triggered a short back-and-forth where Unabyss's MCP tools asked what to prioritize syncing first, rather than dumping everything at once — the whole exchange took under three minutes.
5. Turn the connector on per conversation
Connectors in Claude aren't global by default. Click the + at the bottom left of the chat box, choose Connectors, and toggle Unabyss on for the conversation where you want it active. I left it on for my main work thread and off for one-off unrelated chats, which kept unrelated context from bleeding in.
6. Check what actually synced
Ask Claude directly — "what do you know about me from Unabyss right now?" — and it will list the structured context it has access to. This is the fastest way to catch a source that failed to connect before you rely on it mid-task.
Example prompts you can copy
Once it's connected, the value shows up in prompts that used to need a paragraph of throat-clearing:
- "Pull up what you know about my current sprint from Unabyss and tell me what's blocking [project]."
- "Using my Unabyss context, draft a status update in the tone I usually use in Slack."
- "Check Unabyss for the last thing [teammate] and I discussed about [topic] before you answer."
- "Don't ask me who I am or what I'm working on — check Unabyss first, then ask only what's missing."
- "Summarize what changed in my Notion docs this week, using Unabyss's synced version."
These work because they point Claude at the connector explicitly instead of hoping it reaches for the tool on its own — in my testing, Claude used Unabyss more reliably when a prompt named it directly.
Common mistakes to avoid
The biggest one: connecting every app on day one. I did this on my first pass and ended up with noisier, less relevant answers, because Unabyss had to guess what mattered across a dozen sources instead of a focused two or three. Start with the two or three apps you actually live in — Slack and Notion, say — and add more once you trust what's coming back. Second mistake: forgetting the per-conversation toggle exists, then wondering why a brand-new chat has no memory of anything — it's off by default in each new thread until you switch it on. Third: treating Unabyss as a replacement for Claude's own native memory rather than a companion to it — turn Claude's built-in memory on too, since Unabyss covers cross-app context, not what Claude remembers about your conversation style. Fourth: not checking sync freshness before a task that depends on very recent information — I hit one stale Notion page that was a day behind a real edit, so a quick "what's synced right now" check is worth the ten seconds it costs.
Unabyss pricing
Unabyss dropped its earlier pay-as-you-go credits model in favor of two flat plans, both starting with a 7-day free trial and no credit card required to start:
| Plan | Price | Connected agents | Connected accounts | Best for |
|---|---|---|---|---|
| Pro | $13/mo annual, $15/mo monthly | Up to 3 (via MCP) | Up to 20 | Individuals plugging AI into daily work |
| Max | $79/mo annual, $89/mo monthly | Unlimited | Unlimited | Power users running several AI tools all day |
If you're already on Claude's own Max plan ($100+/month, per Claude’s pricing page) and use two or three tools beyond Claude, Unabyss Pro is the plan that matches — you don't need Unabyss Max just because you're on Claude Max. Save Unabyss Max for genuinely heavy multi-agent setups where the account and agent caps on Pro would actually bind.
Tools that make this easier
Unabyss is a layer on top of Claude, not a replacement for it, so it's worth being solid on the basics first — my how to use Claude AI guide covers accounts, Projects, and prompting before you add a connector on top. If most of what you want synced context for is coding work, pair Unabyss with a proper coding assistant rather than plain chat; see my best AI tool for code comparison and, more broadly, ChatGPT alternatives for coding if you're not committed to Claude Code specifically. For multi-step tasks that go beyond chat — research, browsing, scheduled work — my how to use ChatGPT agents guide is the closest comparison point on the OpenAI side, since agent workflows are exactly where standing context pays off most. Running a small team or a solo business on AI day to day? Best AI tool for small business rounds up the tools worth paying for beyond a single chat connector. And if writing output is your main use case rather than context syncing, my ranked best AI writing tools guide is the better starting point than a memory layer.
My take
Unabyss solves a real annoyance — re-explaining yourself to every AI tool you open — and the Claude setup genuinely takes under two minutes once you have accounts for both. Where I'd pump the brakes: it's a young product (its MCP rebuild only shipped in mid-July 2026), pricing has already changed once, and you're trusting a third party with a synced copy of your Slack, Gmail, and Notion content, which is a bigger ask than it sounds. If you only use Claude and nothing else, native Claude memory plus a solid Project setup covers most of what you need for free. Unabyss earns its $13/month when you're actually switching between Claude, ChatGPT, and Cursor in the same week and are tired of starting cold in each one.
Frequently Asked Questions
Is Unabyss free to use for Claude?
There's a 7-day free trial with no credit card required, but no permanent free tier — after the trial you're on Pro ($13–$15/month) or Max ($79–$89/month).
How long does setup take?
About two minutes for the connector and authorization, plus another two or three for the guided onboarding chat where Unabyss asks what to prioritize syncing. Connecting each source app (Slack, Gmail, Notion, etc.) takes another minute or so per app.
Is Unabyss an official Anthropic product?
No. Unabyss is an independent, MCP-native connector that works with Claude, ChatGPT, Cursor, and other MCP-compatible tools — it isn't built or endorsed by Anthropic. It uses the same open Model Context Protocol that Claude supports for any custom connector.
What's the easiest way to get good results from it?
Connect only two or three apps you actually use daily at first, name Unabyss directly in prompts ("check Unabyss for…") instead of assuming Claude will reach for it, and turn on Claude's native memory alongside it rather than relying on one or the other.
Do I need Claude Pro or Max to use Unabyss?
No — custom connectors work on Claude's Free plan too, though Free accounts are limited to one connector total, per Claude’s help center. Pro, Max, Team, and Enterprise all support Unabyss the same way.