MCP

StoriBot is an MCP server. A tool that speaks the Model Context Protocol, such as Claude, can make Storis, talk to a build, pull the files and manage your organisation, as you.

What you can do through it

Everything the tools do is something you could do in the app, under your own name and rights.

• Make a Stori, or continue one. Start a build on a new Stori or an existing one, send it the brief, answer its questions, turn down a plan, and end it when it is done.
• Follow the work. Read the build’s progress as it happens, and the chat history afterwards.
• Get the files. Pull what the build made: the page, the Word or Excel file, the data behind them.
• Give it files. Upload data and reference material into the session.
• See what is there. List your organisations, Stories, sessions, skills, models and jobs.
• Share. Make, change and remove share links on a Stori, and read or resolve the comments left on one.
• Manage the organisation. Connect a system and set its grants, change the Library, voice and brand, and make or change jobs.

The link a tool hands back is the way into the work. Open it in the app to see the Stori, the share, or the connection it refers to.

How you connect

Add StoriBot as an MCP server in your tool and sign in. The sign-in is StoriBot’s own, the same account you use in the app; the tool never sees your password, and you can revoke its access from the account at any time. Any tool that supports MCP with sign-in works, with no key to paste.

We share the server address with customers once we have walked them through it. Ask the team.

What to know

• It runs as you. A call through MCP has exactly your rights, in the organisations you belong to. It cannot reach an organisation you are not a member of, and an action only an Owner may take is refused for anyone else.
• It spends your organisation’s credits, the same as a build started in the app.
• It is the same StoriBot. The build it starts is the same builder, reading the same Library, memory, voice and brand, with the same grants on the same connected systems. Nothing is different except where you are typing.
• Uploads need the open internet. A file upload ends with a direct post to storage. If your tool runs somewhere that cannot reach it, paste short text into the prompt or give the build a link instead.

The tools

All 13 tools

Tool	What it does
create_stori	Make a new Stori and start a build on it.
start_session	Start a build on a Stori that exists.
talk_to_session	Poll a build’s progress, send it a prompt, answer its question, or turn down its plan.
upload_session_files	Put your files into a build.
end_session	End a build.
get_files	Read what a build made.
get_history	Read a chat’s history.
list_workspace	List organisations, Stories, sessions, skills, models or jobs.
manage_integrations	Connect a system, set what StoriBot may do with it, rotate or disconnect.
manage_assets	Read and change the Library, memory, voice and brand.
manage_jobs	Make, change, pause or delete a job.
share_stori	Make, change and remove share links on a Stori.
share_comments	Read and resolve comments left on a share link.