Migration from SSE to HTTP for improved stability

This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.

The Webflow MCP server has migrated from Server-Sent Events (SSE) to HTTP for improved connection stability and reliability. This change reduces timeout issues and provides a more robust connection between your AI client and Webflow’s APIs.

What’s changing

Previous endpoint: https://mcp.webflow.com/sse
New endpoint: https://mcp.webflow.com/mcp
Protocol: SSE → HTTP

What you need to do

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

Claude Desktop

Cursor

Claude Code

Windsurf

Update your claude_desktop_config.json file:

Old configuration:

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

New configuration:

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

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

Benefits

This migration provides several improvements:

Better stability: HTTP connections are more reliable and less prone to timeouts
Improved error handling: Clearer error messages when connection issues occur
Reduced disconnections: Fewer interruptions when working with the MCP Bridge App
Broader compatibility: Works more consistently across different network configurations

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.