Skip to content

Your agent can build it.
Your client can edit it.

Connect your coding agent through Model Context Protocol (MCP). Create the website, make changes, and manage what goes live from the same conversation.

The browser editor comes with it.

Your client can edit the same site in VoxelSite. Keep the files and the editor on your own PHP hosting.

Connect your agent
  • Inspect or save a view
  • Change the private draft
  • Change the public website
Your coding agentWheelhouse · Example site

You: Build a website for my bicycle repair shop. Three pages: home, our workshop, and contact. Let me review it before it goes live.

  • voxelsite_changes_applyDraft
  • voxelsite_preview_createPreview

Assistant: The three-page draft is ready. I added shared navigation, repair services and a contact form. Open the preview to check the content and layout. Nothing is published yet.

  • index.php
  • our-workshop.php
  • contact.php

Ready for your review

You: I’ve checked the preview. Publish this version and save a snapshot.

  • voxelsite_publish_applyLive
  • voxelsite_snapshots_createSaved

Assistant: The reviewed site is published. I saved a snapshot of this version so we can return to it later.

You: We’re opening on Saturdays. Add a repairs page and link it in the navigation. Keep this in the draft for now.

  • voxelsite_changes_applyDraft

Assistant: Saturday repairs is in the draft, with a new page and navigation link. The original website is still live.

Draft changed · Live site unchanged

You: That looks good. Publish the Saturday repairs update.

  • voxelsite_publish_applyLive

Assistant: The reviewed update is live. The Saturday repairs page and navigation link are now on the public website.

You: We need to postpone. Restore the original public site, but keep the Saturday work in our draft.

  • voxelsite_restore_applyRestored

Assistant: The original site is live again. Your Saturday repairs page and navigation changes are still in the private draft, ready for another day.

Original site restored · Newer draft kept

Back in VoxelSite
VoxelSite’s browser editor, with visual editing controls beside a website preview
Your client’s next edit can happen here.

The agent and Studio use the same private draft. Preview the result, make a manual adjustment, or keep building in the conversation.

Explore the browser editor
Illustrative conversation. Selected tool steps are shown; publication and restoration also require their preparation and review steps. Publishing permission is required to change the live site.

Keep your agent.
Give it a website
to work on.

Model Context Protocol lets your coding agent use VoxelSite’s website tools. The connection points to your installation, with access you control.

Read the connection guide
  1. Install VoxelSite

    Use PHP 8.2+ hosting with SQLite. Run the browser installer and choose external AI or manual editing. You can configure built-in AI later.

    Installation guide
  2. Create a connection

    As the Owner, open Settings → AI tool connections. Choose the account and access level, label the connection, and copy its endpoint and one-time credential.

  3. Add it to your coding agent

    Use the setup instructions shown in Studio. Store the credential in your client’s environment or secret manager. Start by asking the agent to inspect the site.

    Keep the credential out of prompts, screenshots and source control.

The conversation stays
in your agent.
The website stays yours.

Use the agent for a new page or a larger redesign. Open Studio for a text edit, a visual check or client handover. Both work on the same draft and history.

Room to change your mind

Pages, site data, CSS, JavaScript and assets stay in the private draft while you work. A preview lets you check them together.

A version you can inspect

Review the file changes and the rendered page. If another edit changes the draft, the old publication review no longer applies.

A return path

Review a restore from a saved snapshot. Return the live website to that state while keeping your newer draft when needed.

Website snapshots cover the website. Keep hosting backups for the installation, inbox records, accounts and configuration.

Choose what
each connection
can do.

Connect agents you trust. PHP authoring is code access to your site, and publishing is access to its public version.

Read the permission guide

Inspect

Read-only access lets the agent inspect permitted site content without changing it.

Edit the draft

Authoring access lets the agent prepare and apply changes. Keep publish access off if you want to publish from Studio yourself.

Publish and restore

These actions require their corresponding permissions and a current review. An agent cannot gain them by asking in a prompt.

Keep sensitive administration with the Owner

Credential changes, reset and other sensitive operations have additional owner approval boundaries. Revoke a connection in Studio when its work is done.

Your agent uses
its own account.

Studio MCP does not send the agent’s work to the model provider configured in VoxelSite.

See running costs
External agent
Your client’s plan, authentication and usage limits apply. Eligible subscriptions may include usage; API accounts may bill it separately.
Built-in Studio AI
Optional. Uses your configured provider API key and separate API billing. The Router and built-in AI review belong to this path.
Website and editor
VoxelSite is free, open-source software. You pay for hosting, domains and other services, and handle backups and maintenance.

Three interfaces.
Different jobs.

Studio MCP manages your website. The public website’s MCP endpoint serves visitors. The REST API is available for your HTTP integrations.

Manage your website

Studio MCP

Connect your coding agent to create and edit a private draft, inspect changes, publish, and restore a saved version. Each connection has its own access permissions.

/_studio/mcp.php

Integrate over HTTP · beta

Agent REST API

Authenticated HTTP operations for scripts and integrations. AI prompt execution needs separate permission and uses the configured provider.

Read about the Agent API

Serve site visitors

Public MCP

Published site information and enabled visitor actions. These tools do not give visitors access to Studio or the private draft.

Read about visitor actions

Before you
connect.

Check the hosting requirements and decide who can edit and publish each client site.

Can I create a whole website through Studio MCP?
Yes. Your connected agent can create pages, shared navigation, styles, data and assets in the private draft. It can also revise an existing site. Check the result in preview before publishing.
Do I need a model API key in VoxelSite?
No model API key is needed for external-agent work through Studio MCP or for manual editing. Your coding agent supplies the model. Built-in Studio AI uses a separately configured provider API key.
Can I use my existing AI subscription?
Your external client uses its own account. An eligible subscription may include that client’s usage; API or Console authentication may be billed separately. The client’s terms and usage limits still apply. Studio MCP does not convert a chat subscription into a provider API key.
Does Studio MCP run the built-in AI Router?
No. Studio MCP applies work supplied by your external agent. The built-in provider, Router, evaluator and design review are part of Studio’s own AI generation path.
Can the agent publish without asking me?
A connection with publish permission can request publication. VoxelSite requires an explicit operation and a current publication review. If you want to publish only in Studio yourself, give the connection edit access without publish permission.
Can my client keep using the browser editor?
Yes. The external agent and Studio work on the same private draft. Give the client their own account. Editors can change code and publish in Studio; there is no content-only role or editorial approval workflow.
What happens if we edit at the same time?
Changes are checked against the draft version they were prepared for. A stale change is rejected instead of silently overwriting a newer edit. Refresh the context and prepare the change again.
What does restoring a website restore?
A website restore returns the selected site files and shared assets. You can restore the public site while keeping a newer draft. It does not rewind submissions, team accounts, connection credentials or immediate-effect Action definitions. Keep full hosting backups too.
Does it need Node.js or a background worker on my host?
No. The packaged Studio runs on PHP 8.2+ with SQLite and the required extensions. MCP requests use PHP. The coding agent runs in its own client, outside your web host.
Can I connect more than one website?
Yes. Each installation has its own endpoint and connection credentials. Name the connections clearly in your client. This does not add a central multi-site dashboard or share one site’s permissions with another.
Is this the same as the public MCP endpoint?
No. Studio MCP is authenticated website management at /_studio/mcp.php. The public /mcp.php endpoint serves published site information and enabled visitor actions. It does not grant visitors editing access.
What happens when I export the site?
A website export excludes Studio, so Studio MCP is not included. PHP exports retain the public read-only MCP tools and basic PHP form handling. Actions and the submission inbox need Studio. Static exports need an external form service on static-only hosting.

Bring your next
website brief.

Install VoxelSite, connect your agent, and try the full workflow on a sample site before your first client handover.