list_projectsLABSCO SUMMARY
Versions and rollback are the tools that make agent-written content survivable.
Letting an assistant edit live pages is fine right up until it rewrites the wrong one, and the difference between a scare and an incident is whether you can put the previous version back in one call. Having rollback in the same tool set as the edit means the recovery path is available to whoever caused the problem. Given the breadth here — schemas, auth configuration, integrations — that safety net is doing real work.
What it is
A site-building platform exposed in full rather than as a publish button. The surface spans content, data modelling and the integrations behind a form.
What you get
- Projects — create, list, check status
- Content — pages and assets with full create, read, update and delete, plus versions and rollback
- Dynamic data — entity schemas and the records against them
- Forms, wired to a large catalogue of third-party integrations
- Analytics and authentication configuration
- Discovery endpoints published alongside, including an OpenAPI description
Requirements
OAuth with automatic discovery for clients that speak HTTP; a bearer token for programmatic use; the usual proxy for stdio-only clients.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Building and publishing a site
Projects, pages and assets from the conversation.
02
Undoing a bad edit
Versions and rollback, in the same connection that made the change.
03
Modelling content
Entity schemas and the records behind dynamic pages.
04
Wiring up a form
Connect it to the third-party service that should receive it.
58 tools
Listed in project docs. Your client may show a different list.
get_project_statuscreate_projectlist_pagesget_pagecreate_pageupdate_pagepatch_pagedelete_pageget_page_versionsrollback_pagelist_assetsupload_assetdelete_assetget_assetpatch_assetlist_entitiescreate_entityget_entity_schemaupdate_entitydelete_entitylist_recordsget_recordcreate_recordupdate_recorddelete_recordvault_list_secretsvault_store_secretvault_delete_secretlist_integrationssetup_integrationexecute_integrationremove_integrationconfigure_formlist_formsremove_formlist_fragmentscreate_fragmentupdate_fragmentdelete_fragmentset_tracking_scriptsget_tracking_scriptsremove_tracking_scriptscreate_edit_sessionget_edit_session_changescreate_scheduled_tasklist_scheduled_tasksdelete_scheduled_tasklist_tasksget_taskcreate_taskadd_task_historyget_task_historyexport_tasksconfigure_visitor_authget_visitor_auth_configget_analyticsget_integration_schemaBEFORE YOU INSTALL
What to know first
Tools you get
58 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth with automatic discovery as the main path, or a bearer token for programmatic access
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.websitepublisher.ai/Requirements
- OAuth with automatic discovery as the main path, or a bearer token for programmatic access
