WeWeb
WeWeb bets on AI agents building the frontend, with MCP as the on-ramp
◆Recent moves
- 3d ago
🤖 MCP support: build in WeWeb with your AI tool of choice
⚡ SPARKMCP support is the clearest signal yet of WeWeb's AI-native turn: instead of only generating UI inside the editor, it now lets external AI tools read and build in a project directly. It fits the arc from multi-page AI generation toward agents as a primary build surface.
- 3d ago
🚀 Improved Supabase Select, formula columns, and better AI element support
A redesigned Supabase Select, formula columns in table views, and broader AI element support deepen the two areas WeWeb keeps leaning on: its database integration and its AI building surface. Incremental, but squarely on the arc toward AI-assisted, data-backed apps.
- 17d ago
📣 Easier navigation and Popup management
Easier navigation and popup management plus a batch of quality-of-life fixes. Maintenance-grade work that keeps the visual editor usable as the AI and data features pile on top of it.
- 23d ago
Table View editing, Slider actions, easier WeWeb Auth setup
Better Table View editing, new Slider actions, more control over Rich Text Inputs, and simpler WeWeb Auth setup. A grab-bag of editor and data-binding refinements rather than a directional move.
- 1mo ago
🚀 Navigate complex layouts faster with repeater labels
Repeater labels make complex, deeply nested layouts faster to navigate in the editor. Useful for power users building data-heavy apps, but an editor-ergonomics gain rather than a new capability.
- 1mo ago
🧩 Cleaner and more customizable building experience
Framed as letting users build with AI, visually, or by switching between both, this release is the positioning statement behind the trajectory: AI and the visual editor as equal, interchangeable paths. The shipped changes themselves are incremental editor refinements.