Beta release: New tools and improved functionality

The Webflow MCP server beta includes major improvements: a migration to Streamable HTTP, consolidated tools, enhanced security, and new enterprise capabilities. This release provides better connection stability and a more streamlined development experience.

This beta release is available only to Official Webflow MCP Testing partners. To join, contact us at developers@webflow.com.

What’s changing

Previous Endpoint	New Beta Endpoint
`https://mcp.webflow.com/sse`	`https://mcp.webflow.com/beta/mcp`

Protocol: SSE → Streamable HTTP
Data tools: Consolidated from 46+ tools to 18 with the same capabilities
Authentication: More secure auth page
New enterprise tools: Manage 301 redirects, robots.txt, and well-known files
New features: Read-only comments tool and page-level script management

What you need to do

Update your MCP server configuration to use the new beta endpoint. Instructions vary by AI client:

Claude Desktop

Cursor

Claude Code

Windsurf

Update your claude_desktop_config.json file:

New beta configuration:

1 {
2   "mcpServers": {
3     "webflow-beta": {
4       "command": "npx",
5       "args": ["mcp-remote", "https://mcp.webflow.com/beta/mcp"]
6     }
7   }
8 }

After updating, restart Claude Desktop (command/ctrl + R).

Benefits

This beta release provides several improvements:

Better stability: Streamable HTTP connections are more reliable and less prone to timeouts
Simplified toolset: 46+ data tools consolidated to 18 with the same capabilities for easier discovery
Enhanced security: More secure authentication flow protects your account
Enterprise features: New tools for managing 301 redirects, robots.txt, and well-known files
Improved collaboration: Read-only comments tool for viewing site feedback
Better control: Page-level script management for precise customization

If you experience any issues after migrating, try refreshing your OAuth token by running rm -rf ~/.mcp-auth and reauthorizing your sites.

Need help?

If you encounter issues with the migration, visit our FAQs page or open an issue on GitHub.