The read side is unremarkable — databases, schemas, pages, recent updates. The write side is where it differs: creates, updates and deletes each sit behind their own confirmation flag and pages are backed up first, which makes granting edit rights a smaller decision.
A Notion integration server that exposes the workspace as MCP resources — databases and their schemas, database contents, individual pages and recent updates — plus the tools to modify them. Create, update and delete each sit behind their own confirmation switch, on by default, and pages are backed up before they change.
- Every database in the workspace listed, and a database's schema read
- All pages in a database retrieved
- A page's content read by ID
- Recent updates and changes across the workspace
- Confirmation required before create, update and delete, each toggled separately
- Page backups written to a backup directory, kept for a retention window and capped per page
- Block nesting depth capped, and an update polling interval you set
Node.js v16 or higher, and a Notion API key from your Notion integrations page, supplied in the environment. The workspace has to be connected to that integration with the permissions you intend to use. The repository is cloned, built with npm run build, and started with npm start.