Replace Socket.IO designer bridge with page-automation REST API#123
Closed
Replace Socket.IO designer bridge with page-automation REST API#123
Conversation
Remove the Socket.IO-based designer extension tools (de_*) that required an active Webflow Designer browser session. Replace with dynamically registered page-automation tools (pa_*) that call the page-automation REST API endpoints (GET /v1/page-automation/tools, POST /v1/page-automation/execute). Key changes: - Add PageAutomationClient HTTP client with 409 schema-staleness retry - Add dynamic tool registration that converts JSON Schema → Zod at startup - Remove 13 files: Socket.IO bridge, de_* tools, schemas, utils - Remove dependencies: socket.io, cors, express - Graceful degradation: data API tools still work if page-automation is unavailable Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
|
oh this should actually go to https://github.com/webflow/mcp-remote-cloudflare-server! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
de_*) with dynamically registered page-automation tools (pa_*) that call REST endpointsPageAutomationClientHTTP client with 409 schema-staleness retry logicGET /v1/page-automation/toolsand converts JSON Schema → Zod at startupde_*tools, schemas, utils) and dependencies (socket.io,cors,express)Motivation
The
de_*tools required an active Webflow Designer browser session via Socket.IO RPC, which was fragile and limited to local development. The page-automation REST API works without a designer session and the tool manifest is fetched dynamically, so new tools are available as soon as they're added server-side.Tool Parity
Page-automation currently exposes 6 tools (vs 58 actions in the old
de_*tools):get-all-elementsget-element-childrenget-style-by-nameget-style-propertiescreate-styleset-style-propertiesMissing capabilities (pages, element writes, assets, components, variables) will be added as page-automation expands.
Configuration
WEBFLOW_TOKENPAGE_AUTOMATION_API_URLhttps://api.webflow.comTest plan
npm run build)pa_*tools alongsidedata_*toolspa_get_all_elementsreturns elements for a valid site/page🤖 Generated with Claude Code