Connect your website to your AI assistant
If you already work with an AI assistant every day, your website should be something it can reach. MCP is the standard that makes that possible.
What MCP actually is
The Model Context Protocol is an open standard for letting an AI assistant talk to an external system through defined tools rather than screen-scraping.
StoryPages ships an MCP server, so an assistant you already use can query your workspace and act in it.
What you can do with it
Ask your assistant which contacts came in this week and what tagged them. Draft a new page and publish it. Update a price across your site. Pull the enquiries from a campaign into a summary.
The point is not novelty; it is that your website stops being a separate destination you visit and becomes part of the workflow you already have.
Access is scoped and revocable
Access uses workspace API keys with explicit read or write scopes, created and revoked by you. A read-only key can never change your site.
This matters: an assistant with unbounded write access to your public website is not a feature, it is a hazard.
MCP for Claude & ChatGPT, specifically
Native MCP server
Connect Claude, ChatGPT, or any MCP-capable client.
Scoped keys
Separate read and write scopes per key.
Revocable at any time
Remove access without touching your site.
Works with the ecosystem
StoryOS exposes MCP too, so one assistant can span your public site and internal data.
MCP for Claude & ChatGPT: questions we get
Which assistants can connect?
Is this safe?
Do I need to be technical to set it up?
Does this cost extra?
Can it edit my live site without asking?
Go deeper
Other features
See it working on your own business.
Free to start. Describe what you do and you will have a real site to judge in minutes.