AI Prompt to Check Story Continuity Using a Notion MCP Story Bible
This Notion MCP prompt is for novelists and worldbuilders who keep their characters, timeline, and locations in a Notion story bible and want ChatGPT or Claude to catch continuity errors in a new chapter draft by reading that bible directly, instead of relying on the writer's memory of their own canon. Once Notion's MCP server is connected, the model can pull the relevant character and timeline pages and check a draft chapter against them in one pass.
The prompt is built around a specific failure mode: writers lose track of small details across a long manuscript — a character's eye color changes, a scar moves sides, two events happen in the wrong order, a secondary character is in two places at once. Because the model reads the live Notion pages rather than a summary the writer types from memory, it catches contradictions the writer may not even remember establishing. The output is a list of flagged inconsistencies with the exact Notion page and line that conflicts, not a general edit of the prose.
This works best as a pass run after each chapter or scene, before the writer moves on, rather than saved up for a full-manuscript review at the end.
Prompt template
Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.
Example input
When to use it
- Checking a freshly drafted chapter against an established Notion story bible before moving to the next scene
- Reviewing a manuscript for continuity before sending it to beta readers or an editor
- Verifying a new scene doesn't contradict a character's established timeline, appearance, or relationships
- Auditing a long-running serial or web novel where early chapters are easy to lose track of
Best practices
- Point the model at specific Notion pages (character sheets, timeline) rather than the whole workspace, so it isn't guessing which pages are canon
- Ask it to quote the conflicting line from both the draft and the story bible, not just describe the conflict in general terms
- Run the check per chapter rather than waiting for a full draft, since contradictions compound the longer they go unnoticed
- Keep the story bible pages themselves updated as you write, since the check is only as reliable as the source data it reads
Common mistakes
- Asking for a general edit of the chapter instead of a focused continuity check, which buries real contradictions under style notes
- Not telling the model which details are intentionally ambiguous or unresolved, so it flags deliberate mysteries as errors
- Treating the story bible as optional context instead of the source of truth, which leads to the model trusting the draft over established canon
- Skipping the check on short chapters, which is exactly where small details get introduced and then forgotten
FAQs
Can ChatGPT or Claude read my Notion story bible automatically?
Only if your AI client is connected through Notion's MCP server, which lets the model fetch specific pages directly. Without that connection, you'd need to paste the relevant character and timeline details into the prompt yourself.
How detailed does a Notion story bible need to be for this to work well?
It needs the specific facts you care about checking — physical details, dates, and relationships — written explicitly as text. A story bible that's mostly mood boards or loose notes won't give the model enough to compare against.
Should I run this check on every chapter or just before publishing?
Running it chapter by chapter catches contradictions while they're easy to fix; saving it for one pass at the end means untangling errors that may have compounded across many chapters.
What tool pairs well with this prompt if I want to improve it over time?
Prompt Builder — useful for turning a rough description of your continuity-checking needs into a more complete structured prompt as your story bible grows more complex.