yenhao-huang Notion MCP Operations
Workflow
- Read
STATE.md; reset it fromreferences/template/STATE.template.mdfor a new run. Identify the target page, source files, desired structure, and whether the user requested append, update, or full replacement. - Confirm the Notion connector is available with a harmless read or search. If it is unavailable or unauthenticated, stop and report the exact setup or permission blocker.
- Read the current target and all named local source files. Preserve existing linked subpages and unrelated sections.
- Apply the smallest requested write. Use full replacement only when the user explicitly requests a full rewrite.
- Read the affected page again and verify the expected headings, content, and
links. Record target, operation type, and verification evidence in
STATE.md.
Rules
- Use the connected Notion tools directly; do not launch another Codex CLI process to perform the same operation.
- Treat local files as source of truth when the user supplies them.
- Never delete a page or database unless explicitly requested.
- If permissions fail, ask the user to share the target with the connected Notion account rather than retrying blind writes.
Output
Return the page URL, operation performed, verified result, and any skipped or blocked content.