Tools and coverage
Find the tools available to your credential and understand the boundaries of website, business and administrative operations.
Studio MCP exposes typed tools with bounded inputs and outputs. The available catalog depends on the credential’s current permissions. Ask your client to discover tools through MCP tools/list; use the returned schemas rather than a copied list of arguments from another release.
Practical tool groups
| Group | Typical tasks |
|---|---|
| Site context and rules | Read the draft, authoring rules, navigation readiness and an action brief |
| Website changes | Review and apply files, pages, navigation, sections, assets and CSS compilation |
| Preview and publication | Render a draft, open a temporary preview, review publication or take a site offline |
| Website history | Inspect revisions, snapshots, designs and supported restoration |
| Export | Prepare a portable PHP or HTML website archive |
| Business workspace | Work with forms, Actions, submissions, notes, Board and permitted history |
| Configuration and administration | Manage permitted settings, prompts, diagnostics and reviewed owner operations |
Useful starting tools include voxelsite_site_get, voxelsite_site_context and voxelsite_authoring_brief. The change flow uses voxelsite_changes_prepare, voxelsite_changes_get, voxelsite_changes_diff and voxelsite_changes_apply. Retained operations have separate status, continuation and recovery tools.
Supported outcomes have boundaries
Authoring briefs cover tasks such as adding a page, editing a section, restyling or preparing imported source. The external client produces the proposed source. Availability of a recipe does not certify the model’s writing or design quality.
Visual edits use exact, uniquely identified source and content hashes. They can represent text, class, attribute and block changes, including a reviewed parent-block replacement for reordering. They are not unrestricted DOM-selector automation. Ambiguous or stale source must be refused and reviewed again.
Historical native Site plans can be read within account and size bounds. A supported ready plan can be converted into a new change review; reading it does not run or recover the old operation.
What stays outside
The private endpoint does not execute built-in AI generation. Fresh owner approval, one-time secret delivery and factory-reset completion have separate Studio controls. Public visitor data and the REST Agent API are distinct interfaces. Unshipped Collections and Contacts routes are not available tools.
Exports omit Studio management, its credentials and private records. Portable PHP can include a read-only public MCP endpoint; HTML export omits it. Action execution requires the original installation. Included standalone forms still need PHP and have fewer capabilities than Studio forms. Read the archive’s EXPORT-README.txt before deployment.
See Permissions when an expected tool is absent, and Administration before granting owner operations.
Found a mistake in these instructions? Open an issue.
Download VoxelSite