Storywright integrations and tools to use alongside it

Keep maps and encounters in Foundry, character sheets in D&D Beyond, and table chat in Discord. Use Storywright for people, places, promises, and session history.

What connects and what stays separate

• Compatible AI assistants through MCP. Sign in through Storywright to let a supported assistant look up records or draft notes. Support, availability, and permissions vary by client.
• Discord. An incoming webhook tells the party a briefing is ready and links to it.
• Foundry, Roll20, or Owlbear Rodeo. Run encounters in your VTT, and open Storywright when you need people, places, or session history.
• D&D Beyond or system character sheets. Keep statistics on the sheet, and keep goals, relationships, and journals in Storywright.
• Notes from Notion, Obsidian, Google Docs, Kanka, or World Anvil. Copy text into beta paste import where enabled, then review the suggested entries before saving.

Ask an assistant what the party left unfinished

Before the party returns to a town, ask a connected assistant: “What did we promise the people here?” Have it name the entry or session behind each answer. Check those sources before you build tonight's scene around a promise.

The connection uses Model Context Protocol (MCP), which lets compatible assistants look up records and use tools. Sign in through Storywright and review the requested access. OAuth gives the assistant an access token, not your Storywright password.

The connection follows your account across every world it can open. Naming one world in a prompt does not narrow that access. A player who connects their own account still can't open GM-only notes.

For lookups, choose read-only access when the client offers it. A prompt asking to see a draft is not a permission control and does not remove write access you already approved.

With write access, some tools can save directly. Storywright does not add a separate approval step to every write. Confirmation behavior depends on the assistant client, so use its confirmation controls where available.

See supported assistants and setup steps.

Read how account access works.

Let Discord tell the party the briefing is ready

After a game, publish the session's “Previously on…” briefing in Storywright. With Discord notifications enabled, the chosen channel is notified, so players can catch up before the next game without searching the chat for the write-up.

Storywright posts a short announcement with the briefing title, world name, session number, date, and link. The full briefing stays in Storywright. In the world's notification settings, paste an incoming Discord webhook URL and turn on recap notifications.

Set up Discord with the recap delivery guide.

Choose a channel for the people who should receive the briefing. Anyone with a public briefing link can open it, including people outside the world. Check the text before publishing and keep secrets in GM-only fields.

Keep your VTT open during play

Keep running maps and encounters in Foundry, Roll20, or Owlbear Rodeo. Open Storywright when someone asks, “Didn't we meet this captain before?” Look up the captain's entry or the session where the party met them, then get back to the scene.

Storywright does not natively sync with those VTTs or character sheets. Keep encounters and mechanics in those tools, and use Storywright for goals, relationships, journals, and session history. Update each tool separately.

Move one useful piece of your old notes first

If paste import is available to you, start with a place your party knows well or a recent session. Copy the text from your notes app into the beta importer and review the entries it suggests. It can recognize patterns in structured notes or use AI to sort freeform text into entries.

Check names, look for duplicate entries, and choose who should see each piece. Familiar material makes mistakes easier to spot. Save the entries once they look right, then bring over more.

Paste import copies a snapshot into Storywright. It does not sign in to your source app, and later source edits will not carry over.

Read the Manual's import chapter.

Check current plan limits and AI allowances.

See current product facts and availability.

Start a world with the notes you need for your next game.