One company memory for your team and your AI agents
For B2B SaaS teams. Lorekeep connects Notion, Slack, email and your other tools once, keeps what they know up to date, shows where each answer came from and follows who can see what.
- 01
Connect once
Notion, Slack, email and the other tools your team already writes in.
- 02
Stays up to date
When a page or thread changes, the memory changes with it.
- 03
Every answer has a source
Each fact links back to where it came from, and access rules carry over.
- 04
Ask in Slack or over MCP
Your team asks in Slack. OpenClaw, Hermes, Claude, ChatGPT and Cursor connect over MCP.
Why the same questions keep coming back
What your company knows sits in Notion, Slack and email threads.
People can’t find it, so they ask a colleague again, and every AI agent sees a slice of it, so you explain it again.
Meanwhile the old answers go stale.
One memory that stays current and shows its sources
Connect your tools once. Lorekeep keeps what they say up to date, remembers where each fact came from and follows who can see what. The examples are made up.
Notion, Slack and Gmail connected
2,140 pages and threads read, each with its own access rules.
- What happens
- Nobody sees an answer from a page they couldn’t open before.
Your tools go in once, and everyone asks the same memory
Staff ask it in Slack. Any agent that speaks MCP, such as OpenClaw, Hermes, Claude, ChatGPT or Cursor, connects to the same memory to ask questions and add what it learns.
What it reads
- Notion
- Slack
- Your other tools
One memory
- Lorekeepsources and access
Who asks it
The same answer, with its source
- SLYour teamIn Slack
- AIClaude, ChatGPTOver MCP
- AGCursor, OpenClaw, HermesOver MCP
Each answer follows who can see what
Every fact with its source, its age and who can see it
A look inside the memory. Each fact keeps where it came from, when it was last checked and who is allowed to see it. The numbers here are made up.
Facts kept4,812
Tools connected6
Questions answered in Slack318
| Fact | Source | Last checked | Who can see it | Status |
|---|---|---|---|---|
| Refunds within 30 days | Notion · refund policy | Today | Everyone | Current |
| SSO is on the Business plan | Notion · pricing | 3 days ago | Everyone | Current |
| Billing retries webhooks 3 times | Cursor session | Yesterday | Engineering | Current |
| Last agency’s monthly fee | Slack · #finance | Last week | Finance | Restricted |
| Onboarding call length | Email · sales team | 2 months ago | Sales | Needs a check |
A source on every answer
Each answer links back to the page, thread or email it came from.
Access carries over
If you can’t open it in Notion or Slack, you won’t get it as an answer.
Old facts get flagged
A fact nobody has checked in a while is marked so someone confirms it.
How teams find answers today, and where Lorekeep fits
Most teams search each tool on its own, keep a wiki someone has to update, or paste context into each AI chat. Lorekeep keeps one memory with sources that people ask in Slack and agents reach over MCP.
Lorekeep Memory One company memory with sources, kept current, asked in Slack and over MCP. |
Search in each tool | A team wiki | Each AI tool’s memory | Asking a colleague | Lorekeep |
|---|---|---|---|---|---|
| One place to ask Across Notion, Slack, email and more. | One tool at a time | If it was written down | Inside that tool | If they know | |
| Stays up to date Changes in the source show up in the answer. | When someone edits it | Varies | In their head | ||
| Shows where it came from The page, thread or email behind the answer. | Sometimes | Varies | |||
| Follows who can see what Each tool’s own permissions. | Its own rules | Varies | Depends on them | ||
| AI agents can use it Ask questions and add what they learn. | In that tool | Over MCP |
Early access
10+ people
B2B SaaS teams
For B2B SaaS teams whose answers live in too many tools.
- B2B SaaS companies, best from about 10 people up
- Knowledge spread across Notion, Slack, email and more
- AI agents like Claude, ChatGPT or Cursor in daily use
Common questions
It connects the tools your company writes in, such as Notion, Slack and email, and keeps one company memory that stays up to date. It records where each fact came from and follows who can see what. Your team asks it in Slack, and AI agents connect to it over MCP.
Notion, Slack and email, plus the other tools your team writes in. You connect each one once.
In Slack, the way they’d ask a colleague. Each answer links to the page, thread or email it came from.
Any agent that speaks MCP, such as OpenClaw, Hermes, Claude, ChatGPT and Cursor. They can ask questions and add what they learn, so you stop explaining the same context to each one.
Yes. Access follows each tool’s own rules, so people and agents get answers from what they’re allowed to see.
It keeps reading the tools you connect. When a page or thread changes, the memory changes with it, and facts nobody has checked in a while are flagged.
Every answer shows its source and when that source was last updated, so you can open it and check.
B2B SaaS companies, best from about 10 people up, where knowledge sits across Notion, Slack, email and other tools.
We’re setting the price with our early-access teams. Join the waitlist and you’ll see it before you commit to anything.