Writing long-form or a series
The further you go, the more you have already decided.
Structured story bible
Scenes, characters, worldbuilding, foreshadowing, plot threads. Everything you decide while building a story, kept in one fixed shape — and connected to Claude, ChatGPT or Claude Code over MCP, so your AI reads and writes it directly instead of being told again every session.
A StoryCanon account is required. Sign in with Google.
StoryCanon is for the kind of writing where there is simply too much to remember — long-form fiction, a series, a campaign scenario, a world you keep adding to.
The further you go, the more you have already decided.
The conversation moves on. What you settled should not move with it.
TTRPGs, games, pitches — a lot gets decided before a word is written.
You don't pick a template and fill in the blanks. Every project has the same shape, so a character always has a goal, a secret and a current state — and nothing important ends up in a field you forgot to add.
Body text, summary, what happened, and the order they're read in.
Title, order, summary and purpose, with scenes assigned to them.
Role, age, personality, speech style, appearance, background.
Categorised as inner life, relationships, background, speech or plot.
Places, organizations, technology, history, culture, items and rules.
What is running, where it stands, and what would resolve it.
Where it was planted, how it's meant to pay off, whether it has.
The question, the truth, who knows it, the clues, the reveal point.
The problem, a suggested fix, a priority, and who raised it.
An append-only history of where the story stood at each point.
In-story events in order, tagged, with the characters each one involves.
Genre, premise, tone, audience, style, and elements to avoid.
Where you stopped reading, per project.
There is no template picker, because there is nothing to pick. One opinionated schema, applied to every project.
StoryCanon does not generate text itself. It is the place your AI writes into — so the story it helps you build is still there tomorrow, and still yours to change your mind about.
A few steps in Settings and your assistant can read and write your project directly. No plugin, no browser extension, nothing to install.
Your premise, the latest story state, the cast, the open plot threads and the unresolved foreshadowing all go over together — so the AI starts every session already knowing where the story is.
When the AI takes the story somewhere you didn't want, telling it to undo that is enough to put things back. You don't have to remember what it touched or repair anything by hand — and nothing is really deleted along the way.
Scenes and revision TODOs remember whether they came from you or from an assistant, so a draft you meant to rewrite never quietly becomes canon.
I want to go deeper on Goda, without contradicting anything already decided about him.
Reading his profile and the notes filed against him.
get_characterHe keeps what he knows separate from what he can say, speaks in flat endings, and never uses Akari's name. The one thing not written down is why he stays silent — and it has to square with his cutting the pier lights that night.
That's the gap. Work it out and write it down.
Added two character notes: the reason for his silence, and how he keeps his distance from Akari.
save_character_noteHis current state is updated too, so the next session starts from this and not from scratch.
save_characterNothing was pasted in. The context came from the work itself, and the result went back into it.
StoryCanon runs a Model Context Protocol server, so it fits the tool you already use. Any MCP client can point at a single endpoint and work with your project — one URL and a sign-in, with nothing to install on either side.
Add StoryCanon as a connector and approve it in the browser — the URL alone is enough, with no token to copy anywhere. Claude Code connects with a single `claude mcp add` command, carrying an API token from your Settings page.
Turn on developer mode and add StoryCanon as a custom app: the URL alone is enough, and OAuth handles the rest. A Custom GPT can also reach it through Actions and the published OpenAPI schema.
Prefer to keep the model on your own machine? Use an MCP client that runs against Ollama and it reaches the same endpoint, so your text goes to a model you host rather than to a hosted service.
Anything else that speaks MCP works the same way. The endpoint and the connection steps — plus an API token, for the clients that need one — are all on the Settings page once you sign in.
StoryCanon is an independent service, and is not affiliated with, endorsed by or sponsored by any of these companies. Their names appear here only to identify the tools StoryCanon can connect to.
Everything an AI could write here, you can write yourself. Using StoryCanon purely to keep a scenario and its worldbuilding straight is a first-class way to use it.
Every entity has an ordinary form, with inline editing on the pages you are already reading.
Read your manuscript without the editing interface. Your scroll position is saved as you go and restored per project.
World notes and character notes carry a category and an importance, and stay attached to the scene they came from.
Export the manuscript and everything around it as Markdown or plain text on any plan, or as structured JSON on a paid one.
Start free. Upgrade when you need more projects, more manuscript, or structured export.
To get started
$0 / month
For writing regularly
$9.90 / month (tax incl.)
$99 / year · 2 months free
For long-form and series
$52.80 / month (tax incl.)
$528 / year · 2 months free
Prices include tax. The final amount is shown on the Stripe checkout page.
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Projects | 3 | 50 | 500 |
| Characters (per project) | 8 | 20 | 200 |
| Body text (characters per project) | 20,000 | 100,000 | 1,000,000 |
| World notes (per project) | 30 | 200 | 2,000 |
| Foreshadowing (per project) | 30 | 100 | 1,000 |
| Mysteries (per project) | 30 | 100 | 1,000 |
| Plot threads (per project) | 30 | 100 | 1,000 |
| Revision TODOs (per project) | 50 | 300 | 3,000 |
| Story state snapshots (per project) | 10 | 100 | 1,000 |
| JSON export | — | ✓ | ✓ |
Limits are per project unless the row says otherwise.
If something here is still unclear, the contact form goes straight to the developer.
StoryCanon is developed and run by one person. That shapes what you can expect from it.
Opens a form. No account needed.
Free to start, and yours to export at any time.
Start for freeSign in with Google.