Bring your assistant to the desk

Connect in three steps

You sign in through Storywright's own login and consent screen — your assistant never sees your password. It receives a scoped access token instead, limited to reading your worlds and, if you grant it, writing journal entries, quests, and lore.

What this is

Storywright keeps the record of your world: sessions, recaps, player journals, quests, and the lore in your Drafting Table. If you already work with an AI assistant, you can seat it at that desk. Storywright runs a server for the Model Context Protocol (MCP) — the open standard Claude, ChatGPT, and a growing number of tools use to reach outside services.

Once connected, your assistant can look things up mid-conversation — “what happened in our last session?”, “which quests are still open?”, “what do we know about the harbormaster?” — and, when you ask it to, write back: draft a journal entry, log a quest, file a Drafting Table entry, or sketch a session recap for you to review.

Good first moves

The connector ships ready-made prompts — in Claude they appear as commands you can pick straight from the prompt menu:

/start-new-campaign

No world yet? Pick a genre template — high fantasy, sci-fi space opera, modern mystery, or a guided blank slate — and it builds the world and reports back what got seeded.

/prep-my-next-session

A GM prep packet: where the story left off, open threads, and who's likely to show up.

/what-happened-last-session

A chronicle-keeper's recap of the latest session, drawn from its notes, recap, and player journals.

/find-loose-threads

Dangling quests, unkept promises, and forgotten corners of the world — each with a suggested re-hook.

/catch-me-up

For players: everything you missed, your character's situation, and what the party is chasing now.

/import-campaign-module

Hand it a prepared campaign — a published module, a Notion export, your own notes — and it fills the world: locations, NPCs, story arcs, and the beats between them. It reads the document on your side and shows you a plan before it writes anything.

Check that it worked

“Connected” in your assistant's settings means the sign-in succeeded — not that it can read your campaign. Four questions settle it:

• “What Storywright worlds can you see?”It should name your worlds back to you.Says it has no access — the connector was added but never authorized. Remove it and add it again.
• “What happened in our last session?”Check a detail you remember — it should get it right.Confident prose about a session that never happened means it is answering from imagination, not from the record.
• Try a ready-made prompt — in Claude, type /find-loose-threads.If the commands don't appear in the menu, the client connected but hasn't loaded the prompt list; reconnect it.
• Ask it to write something small — a one-line journal entry. Then look for it in Storywright.If it reports success and nothing appears, it was granted read access only; reconnect and approve writing.

If a step fails and reconnecting doesn't fix it, write to [email protected] and say which of the four it was — that alone usually names the problem.

What it can and can't do

A connected assistant acts as you, with exactly your permissions — every request runs through the same checks as the app itself, enforced on the server.

• A player's assistant sees what that player sees. GM notes, hidden lore, and unrevealed entries stay hidden — connecting an assistant never widens anyone's view of the world.
• GM-only actions — publishing a session briefing, touching GM notes — are refused when a player's assistant attempts them, just as they would be in the app.
• Anything it writes lands as ordinary entries under your name, which you can edit or delete like anything you typed yourself. Nothing skips the reviews and approvals your table already relies on.

Disconnecting

Remove the connector in your assistant's settings whenever you like. Storywright supports standard OAuth token revocation, so a client can surrender its token the moment you remove it — and the tokens are short-lived besides: access tokens expire after about an hour and are renewed only while the connection is in use, and a connection left idle lapses on its own within thirty days. If you ever want a connection cut off immediately and removing the connector isn't enough, write to [email protected] and we'll revoke it from our side.