Connect an AI agent

Let Claude, or another AI agent, work on your stories directly: draft chapters, fix errors, keep your characters consistent, and publish when you say so. You decide what it may do, and you can take access back at any time.

What it does#

Storyomi speaks the Model Context Protocol (MCP), the standard way for AI apps to use outside tools.

Once connected, an agent can see your stories, check scripts with the same error checker the Studio uses, write and save chapters, manage your characters and variables, and, if you allow it, publish and upload art. It does not need to know OmiScript beforehand: Storyomi teaches it the language, with working examples and the common mistakes, when it connects.

It only ever sees and changes your own stories. Someone else's story looks exactly like one that does not exist.

The Storyomi address#

Every agent app asks for this once.

Storyomi address

https://storyomi.com/mcp

Connect your agent#

Pick the app you use. You sign in to Storyomi in your browser; you never give the agent your password.

Claude (claude.ai and the desktop app)

Add Storyomi as a custom connector.

Open Customize, then Connectors. (On a Team or Enterprise plan, an Owner adds it under Organization settings, then Connectors, and members connect from Customize.)
Click Add custom connector and paste the Storyomi address.
Leave the OAuth client on "Use Claude's published identity". Do not enter a client ID or secret.
Click Add, then Connect. Sign in to Storyomi if asked and approve the permissions you want to give.

Storyomi address

https://storyomi.com/mcp

The Free plan allows one custom connector.
Claude's settings cannot be edited after adding: to change the sign-in settings, remove the connector and add it again.

ChatGPT

Add Storyomi as a custom MCP server.

In ChatGPT, open Plugins and use the plus button, then choose Add custom MCP server.
Paste the Storyomi address and choose OAuth sign-in. If it asks for a client ID or secret, leave them blank: ChatGPT identifies itself to Storyomi automatically.
Read the warning, choose "I understand and want to continue", then Create as a plugin.
Install it, sign in to Storyomi when asked, and approve the permissions you want to give. Then start a chat and ask it to use Storyomi.

Storyomi address

https://storyomi.com/mcp

ChatGPT asks you to confirm write actions in each conversation before it makes them. Expect a prompt before it saves, deletes or publishes.
ChatGPT connects from the internet, so Storyomi must be reachable over HTTPS.
Use it in a normal chat. Deep research and company knowledge expect a pair of tools called search and fetch, which Storyomi does not provide.
ChatGPT typically cannot send files from your computer, so it cannot upload art. Ask it for the list of images your story needs and upload them in Studio.
Whether custom servers are available depends on your ChatGPT plan, and on a workspace plan an admin may need to allow them. Check OpenAI's help for your plan.

Claude Code

One command, then sign in from the browser.

Run the command below in your terminal.
Inside Claude Code, run /mcp and choose Storyomi to sign in (or run the second command from your shell). Approve the permissions in the browser.

Add the server

claude mcp add --transport http storyomi https://storyomi.com/mcp

claude mcp login storyomi

Or share it with a project: .mcp.json

{
  "mcpServers": {
    "storyomi": {
      "type": "http",
      "url": "https://storyomi.com/mcp"
    }
  }
}

In .mcp.json the "type" field is required: an entry with only a url is read as a local program.
Claude Code can run shell commands, so it can upload images and audio for you.

Visual Studio Code

Add it from the command palette.

Open the command palette and run MCP: Add Server.
Choose HTTP (HTTP or Server-Sent Events) and paste the Storyomi address.
Give it an ID such as storyomi and choose where to save it.
Approve the sign-in when VS Code asks, then approve the permissions in the browser.

Storyomi address

https://storyomi.com/mcp

Storyomi identifies apps with Client ID Metadata Documents. Recent versions of VS Code support this; if you see a registration error, update VS Code.

Cursor Not supported yet

Not supported yet.

Cursor signs in with dynamic client registration or a fixed client ID, and does not yet support the Client ID Metadata Documents that Storyomi uses to identify apps. Adding Storyomi to Cursor will fail at sign-in.
Use Claude, Claude Code or VS Code for now.

Permissions#

When you connect, an approval screen lists what the app is asking for. You can untick anything except reading.

Permission	What the agent can do	You can decline
View your stories, chapters, and registries	Read your stories, chapters, characters and assets, check scripts for errors, and learn the OmiScript language from Storyomi.	No
Edit your draft stories, chapters, and registries	Create stories and chapters, edit scripts, reorder, add or change characters, variables and apps, and delete chapters or entries (each deletion needs the exact name confirmed).	Yes
Publish and unpublish your stories	Publish or unpublish chapters and stories. Players can see the result.	Yes
Upload and modify your story assets	Upload, rename and delete images and audio in your story library.	Yes

Working with an agent#

Ask in plain language. A few things worth knowing.

Start with a task. “Create a story called Harbour Lights and write chapter one: Mira confronts the narrator on the pier.” Or “Check all my chapters for errors and tell me how to fix them. Don't change anything.”
It checks its own work. The agent runs every draft through the error checker and fixes what it finds before saving.
No art yet? That's fine. An agent can write scenes that name images you haven't uploaded. Ask it for the checklist (“what images does my story still need, and what should I call them?”), upload each in Studio under Assets with exactly that name, and the story is complete. Storyomi will not publish a chapter with missing art unless you tell it to.
Agents that can run commands can upload art too. The file goes straight to Storyomi (it never passes through the AI), and Storyomi checks it arrived unchanged.
Saving is safe next to the Studio. If you edit a chapter while the agent is working on it, the agent is told and re-reads it; your changes are never silently overwritten.

Safety and control#

You stay in charge of what an agent can do.

See and revoke access in Settings → Connected apps. Changes, publishing and uploads stop immediately. An app that was only reading may keep reading for up to an hour, until its current session expires.
Deletions are deliberate. Deleting a chapter, a character or an image requires the agent to confirm its exact name, and is refused while your scripts still use it unless you tell the agent to go ahead.
Everything is recorded. Storyomi keeps a trail of what each connected app changed and when, never the text of your stories.
Publishing has side effects. Publishing a chapter makes all of the story's uploaded images and audio public, and a chapter's first publication counts as its release.
Your stories are your data. Text the agent reads from your stories is treated as content to edit, never as instructions to follow.

Troubleshooting#

The things that most often go wrong, and what to do.

What you see	What to do
"This authorization request is invalid or has expired"	The approval link only works for a few minutes. Go back to your agent and connect again.
An error about client registration, or the connection fails at sign-in	The app does not support the way Storyomi identifies apps (Client ID Metadata Documents). Cursor does not yet. Update the app, or use Claude, Claude Code or VS Code.
After signing in (with Google or a password) you ended up on a Storyomi page instead of the approval screen	The sign-in link expires after about ten minutes. Start the connection again from your agent. You are signed in now, so it goes straight to the approval screen.
The agent says it can no longer access your account	Access was revoked (by you in Settings, or by reconnecting). Connect it again.
A save fails with a "conflict"	You (or another app) changed the chapter after the agent read it. The agent re-reads the latest text and tries again; your changes are never overwritten.
"Not published: the chapter uses assets that have not been uploaded"	Upload the listed images or audio in Studio, under Assets, using exactly the names shown. Or ask the agent to publish anyway if you are happy with scenes without them.
An upload link was "already used" or "expired"	Upload links work once and last ten minutes. Ask the agent for a new one.