Studio MCP
Connect your AI tool to a private website draft, review changes and choose what it may do.
Studio MCP overview
Work on a VoxelSite website from your own AI tool. Start with read access, review draft changes and publish separately.
Connect Codex
Configure Codex with the private Studio MCP URL and a bearer credential held in a local environment variable.
Connect Claude Code
Configure Claude Code with Streamable HTTP and an environment-variable bearer header for private Studio MCP.
Connect another MCP client
Check Streamable HTTP and bearer authentication support before connecting another MCP client to VoxelSite.
The site lifecycle
Read context, review exact draft changes, apply and preview them, then make a separate publication decision.
Permissions and credentials
Choose account-bound access for reading, draft editing, publication, business records and administration.
Costs and limits
Understand external-client billing, built-in provider billing, hosting limits and bounded Studio MCP requests.
Tools and coverage
Find the tools available to your credential and understand the boundaries of website, business and administrative operations.
Business workspaces
Use scoped MCP access for Actions, submissions, notes and Board while distinguishing real business writes from draft changes.
Administration
Use owner-scoped configuration and reviewed administrative operations without treating chat confirmation as Studio approval.
Troubleshoot Studio MCP
Resolve waiting connections, authentication and permission errors, lost credential delivery and interrupted operations.