Notion backend
Why Notion
- Team-shareable — your knowledge base is already where your collaborators are.
- Rich blocks (toggles, callouts, embeds) for human consumption.
- No host to manage; no Docker; no port to forward.
Set up the integration
- Visit https://www.notion.so/profile/integrations
- Create a new internal integration; copy the secret (
secret_xxxxx) - In Notion, create a page (e.g. “Claude Memory”)
- Open the page → Share → invite the integration
- Copy the page id from the URL
Configure the MCP
export BRAIN_BACKEND=notionexport BRAIN_NOTION_TOKEN=secret_xxxxxexport BRAIN_NOTION_ROOT_PAGE=<root-page-id>Layout in Notion
- Root page: the one you shared with the integration
- Child pages for
Standards,Decisions,Lessons Learned,Apps,Reviews,Drafts - Each
brain_remembercreates a child page under the appropriate category, with title + body + tag-line block
Limitations vs other backends
- Notion API has rate limits —
brain_scan_transcriptsmay need to slow down for large transcript counts. brain_updateis currently append-only — it adds an “updated” block rather than replacing existing block content (Notion’s API requires per-block surgery; PRs welcome).- Tags are added as inline
#tagparagraph blocks rather than database multi-select properties (works without requiring a database). - Search uses Notion’s own search endpoint — less granular than Trilium’s query language.
PRs to expand the Notion adapter (database-backed tags, full block-replacement, multi-select properties) are welcome — see the source.