MCP and API
How AI assistants update your site safely
Workroom exposes the website workflow as an MCP server at workroom.one/api/mcp, authenticated with a workspace-scoped API key. Claude, ChatGPT, or any other MCP client can read the authored files, patch only what changed, publish a new immutable version, and restore an earlier one. The safe default merges a patch instead of replacing the whole site, stale writes are refused, and every successful write becomes a restorable version.
How it works.
Create a workspace-scoped key
Keys are created on the dashboard's MCP / API page and resolve to one workspace. A key can never see another workspace's sites.
Inspect before writing
The client reads a manifest of paths, sizes, and hashes first, then pulls only the file bodies it needs. It reads the authored files — component includes intact — not the compiled page a visitor sees.
Patch, do not replace
The default patch tool merges the files the agent sends into the current site, so pages it never held survive the update. Removing a page through that tool takes an explicit instruction.
Stale writes are rejected
A write can name the version it started from. If the site changed in between, Workroom refuses rather than overwriting work the agent never saw.
Publish and roll back
The result is a new immutable version. It appears in the site's history alongside human edits, and restores the same way.
What to know before you rely on it.
- Site edits through MCP publish immediately — they are not held for approval. The safety net is the version history, not a review queue.
- The full-bundle push tool replaces the whole site and therefore removes pages the caller omits. It is for clients that authored and hold the complete bundle; partial updates should use the patch tool.
- There is no delete-site tool on this surface.
- Keys are rate limited per day and can be revoked instantly. An exhausted key gets a distinct response from an invalid one, so an authentication error always means the key itself.
- Generative calls spend credits the same way the dashboard does. Publishing a bundle the agent generated itself runs no model and costs nothing.
- Routine tools are removed from the tool list while routines are coming soon, so a client never discovers a call Workroom cannot currently fulfil.
Questions, answered.
Which assistants can use this?+
Any MCP client. The server speaks streamable HTTP with a bearer key, so Claude Code, claude.ai connectors, and other MCP-capable clients all connect the same way.
Can an agent see my other sites?+
Only the sites in the workspace its key belongs to. The key resolves directly to that workspace and nothing else.
Keep reading.
How Workroom makes every change reversible
Nothing edits your site in place. Every change writes a new immutable version of the whole bundle, restoring is itself a new version, and your domain only moves when you promote.
BuildingHow Workroom builds a website from one brief
One description of your business becomes a complete site: web research, an architect pass that fixes the design system, parallel page builds, and a homepage that publishes early.
ContextHow Workroom keeps your business facts aligned
One business profile per site — what you do, who you help, your offers, tone, verified facts, proof points, and a never-say list — read by every AI surface that writes for you.
Describe the business. See the site.
Building and previewing is free, and chat editing is unlimited.