runelay+WebflowIntegration · OAuth login
Webflow on Runelay, an open source MCP gateway
Connect Webflow once. Claude Code, Cursor, Codex and Grok all use that connection, and the credential never leaves your server.
What this connection does
Sites, pages and CMS collections. Runelay connects to the Webflow remote MCP server at https://mcp.webflow.com/mcp and puts its tools behind your own endpoint.
Agents find them with search_tools and run them with call_tool, so the Webflow tool list is not loaded into context until it is needed.
Connect Webflow
Open the connectors in the panel
Pick Webflow from the catalog.
Log in once
A browser tab opens on Webflow. Approve the access and close it.
Done
The token is stored encrypted on your server and refreshed by Runelay. Every agent with a Runelay key can use the connection.
Use Webflow in your agents
Agents do not need a Webflow entry of their own. Point each one at Runelay and Webflow is there.
Questions
Does my Webflow credential reach the agent?
No. It stays on your Runelay server, encrypted with AES-256-GCM using your RUNELAY_SECRET. Agents only hold their Runelay key.
Do I connect Webflow once per agent?
No. You connect it once in Runelay, and every agent that points at your endpoint uses the same connection.
I already have Webflow set up in an agent. Can I bring it?
Yes. runelay migrate reads the MCP servers your agents already have. If the CLI can read the token it arrives connected; otherwise it waits in the reconnect queue in the panel.