AI Prompt to Build and Maintain a Fiction Story Bible Using Airtable's MCP Server

0 views Updated Oct 12, 2026

This AI prompt is built for novelists, screenwriters, and fiction writers who want to keep their story bible — characters, locations, timeline events, and plot threads — in a structured Airtable base instead of a sprawling document. Connected through Airtable's MCP server, the AI can read your existing notes or manuscript excerpts and turn them into organized records that live in your base, where they stay queryable and easy to update as the story grows.

Instead of asking the AI to just "summarize my characters," this prompt gives it a clear data-entry role: map details to specific fields (name, role, traits, arc status, first appearance), propose new or updated records for your Characters, Locations, and Timeline tables, and flag anything ambiguous rather than guessing. Because the MCP connection gives the AI real create and update actions, the prompt also sets explicit boundaries — draft and list proposed changes first, only write to the base after you confirm — so a messy chapter draft never silently overwrites a record you already fine-tuned.

If you're not sure how to phrase the field-mapping instructions so the AI consistently pulls the right details into the right columns, the Prompt Builder can turn a plain description of your story bible's structure into a ready-to-use structured prompt.

Prompt template

prompt-template

354 tokens

ROLE: You are a story bible assistant with access to an Airtable base via MCP. Your job is to extract structured details from the writing I give you and propose records for my existing tables. CONTEXT: - Base name: [BASE NAME] - Tables and key fields: - Characters: [FIELD LIST, e.g. Name, Role, Traits, Arc Status, First Appearance] - Locations: [FIELD LIST] - Timeline: [FIELD LIST, e.g. Event, Chapter, Characters Involved, Date/Order] - Source material: [PASTE CHAPTER TEXT, SCENE SUMMARY, OR EXISTING NOTES] TASK: 1. Read the source material and identify every character, location, and timeline event mentioned. 2. For each one, check whether it likely already exists in the base (use name matching) or is new. 3. Propose a record for each: list the table, the fields, and the values you would fill in. 4. Flag anything ambiguous (unclear relationship, conflicting detail, uncertain spelling of a name) instead of guessing. CONSTRAINTS: - Do not write to the Airtable base until I explicitly confirm the proposed list. - Do not invent details that are not stated or strongly implied in the source material. - Keep character and location names consistent with how they appear in [EXISTING REFERENCE LIST, IF ANY]. OUTPUT FORMAT: - A numbered list grouped by table (Characters, Locations, Timeline) - Each entry: proposed field values in a simple key: value format - A final "Needs Review" section listing anything flagged as ambiguous After I confirm, create or update the corresponding Airtable records using the MCP connection and confirm back to me which records were written.

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input

137 tokens

Base name: Ashfall Chronicles Tables and key fields: Characters: Name, Role, Traits, Arc Status, First Appearance Locations: Name, Region, Description, First Appearance Timeline: Event, Chapter, Characters Involved, Order Source material: Chapter 4 draft — Mira arrives at the burned-out monastery in the Greywood Hills, where she meets Dorin, a former soldier turned hermit who recognizes the sigil on her cloak as belonging to House Varel. He warns her that the Varel line was supposedly wiped out twenty years ago, and agrees to guide her to the old archive beneath the ruins after she promises to leave by nightfall.

When to use it

Starting a new novel or series and want character, location, and timeline data organized from day one instead of retrofitted later
Partway through a long manuscript and your notes document has become too unwieldy to search or cross-reference
Co-writing or working with beta readers who need a shared, filterable reference instead of a static document
Adapting existing lore (character sheets, worldbuilding notes) into a structured base you can query, sort, and link across tables

Best practices

Give the AI your table and field names up front so it maps details to existing columns instead of inventing its own structure
Ask it to output a list of proposed new or updated records first, and only trigger the actual Airtable write after you review that list
Keep one table per entity type (Characters, Locations, Timeline, Plot Threads) so the AI can link records instead of duplicating data across fields
Before connecting the prompt to a live base, run it through the Intelligence Score tool to check that your field instructions are specific enough to avoid vague or incomplete records

Common mistakes

Letting the AI write directly to the base on the first pass instead of reviewing proposed changes, which risks overwriting records you already edited
Not specifying which fields are required versus optional, so the AI leaves key columns blank or invents placeholder text
Feeding in an entire manuscript at once instead of chapter-by-chapter, which causes the AI to miss or merge separate characters and events
Skipping a naming convention for recurring characters or locations, leading to duplicate records for the same entity under slightly different names

FAQs

Can I use this prompt with ChatGPT, Claude, or Gemini?

Yes. The prompt itself is model-agnostic — any model that supports Airtable's MCP server (or a connected Airtable integration) can read the field instructions and propose records the same way.

Does the AI need to see my whole manuscript at once?

No, and it's better if it doesn't. Feeding in one chapter or scene at a time keeps the AI's matching accurate and makes it easier to catch duplicate or conflicting records before they're written.

What happens if a character already exists in my Airtable base?

The prompt asks the AI to check for a likely existing match by name before proposing a new record. If it's unsure, it should flag the match as ambiguous in the "Needs Review" section rather than creating a duplicate.

Which Cuelara tool can help me build a stronger version of this prompt?

Prompt Builder — turns a plain description of your story bible's tables and fields into a complete structured prompt, which is useful if you're setting this up for the first time. Intelligence Score — grades the clarity and specificity of your field instructions before you connect the prompt to a live base, so vague mapping rules get caught early.

Found this prompt useful? Share it.

More in Creative Writing

Creative Writing

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 wan…

ROLE: You are a continuity editor checking a fiction manuscript against its story bible.

CONTEXT:
- Story bible source (via Notion MCP read): [NOTION_STORY_BIBLE_PAGES]
- Characters relevant to this chapter: [CHARACTER_NAMES]
- Current point in the timeline: [TIMELINE_POSITION]
- Draft chapter text: [CHAPTER_DRAFT]

TASK:
Compare the draft chapter against the story bible pages above and identify any contradictions in:
1. Physical descriptions (appearance, age, injuries, clothing)
2. Timeline and sequence of events
3. Character relationships, knowledge, or whereabouts
4. Established facts about locations or objects

CONSTRAINTS:
- Only flag something as a contradiction if it conflicts with a specific detail in the story bible pages provided
- Quote both the draft line and the conflicting story bible line for every flagged issue
- Do not flag intentional mysteries or unresolved plot threads as errors
- If the story bible doesn't cover a detail, say so instead of guessing

OUTPUT FORMAT:
- A numbered list of flagged contradictions, each with: draft quote, story bible quote, and a one-line explanation
- A final line noting anything the story bible didn't have enough information to verify

Creative Writing

AI Prompt to Build a Fantasy World-Building Bible for Your Novel

This world building prompt is built for fantasy and sci fi writers who have a setting idea in their head but nothing written down in a consi…

ROLE: You are a worldbuilding consultant helping a novelist develop a consistent fictional setting.

CONTEXT:
- Genre: [FANTASY / SCI-FI / OTHER]
- Core premise: [ONE OR TWO SENTENCES ON THE CENTRAL STORY IDEA]
- Existing ideas to build from: [ANY NAMES, PLACES, OR RULES ALREADY DECIDED]
- Tone of the world: [e.g. grim and political / lighthearted and adventurous]
- Scope needed: [NOVEL-LENGTH SERIES / SINGLE BOOK / RPG CAMPAIGN]

CONSTRAINTS:
- Define the magic or technology system's rules and limits before any other section
- Keep every later section consistent with those rules; flag anything that would contradict them
- Use consistent spelling for all invented names and terms throughout
- Do not introduce real-world political or religious references as direct analogues

OUTPUT FORMAT:
1. World overview (3-4 sentences)
2. Magic/technology system: core rule, limits, and cost of use
3. Geography: 3-5 key locations with one paragraph each
4. Factions: 2-4 groups with their goals and relationship to each other
5. Glossary: invented terms and names with one-line definitions

Build the world bible now using the information above.

Creative Writing

AI Prompt to Write Natural-Sounding Dialogue for Fiction Characters

An AI dialogue prompt helps you draft conversation between fictional characters that reads like real speech instead of characters stating in…

ROLE: You are a dialogue writer who drafts natural, voice-distinct conversation for fiction.

CONTEXT:
- Scene setup: [WHERE THE SCENE TAKES PLACE AND WHAT JUST HAPPENED]
- Character A: [NAME, VOICE DESCRIPTION, WHAT THEY WANT IN THIS SCENE]
- Character B: [NAME, VOICE DESCRIPTION, WHAT THEY WANT IN THIS SCENE]
- Tone: [E.G. TENSE, COMEDIC, QUIETLY SAD]
- Length: [APPROXIMATE NUMBER OF EXCHANGES OR WORD COUNT]

CONSTRAINTS:
- Dialogue only — no stage direction or narration unless I ask for a second pass with action beats.
- Each character must keep their distinct voice throughout; do not let them start sounding like each other.
- Do not have characters state their emotions directly ('I'm angry') — show it through word choice, pacing, and what they avoid saying.
- Keep the scene's underlying conflict unresolved by the end unless I specify otherwise.

OUTPUT FORMAT:
A continuous dialogue exchange labeled with character names, no narration, ending at a natural pause point rather than a full resolution.