DIVE vs Dialkit

Both are browser-based visual editors. DIVE's differentiator is the MCP handoff and the persistent, exportable change history.

Dialkit and DIVE share the in-browser editing premise. The fork in the road is what you do with the edits, DIVE treats them as a structured diff to ship to engineering or an AI agent.

Pick DIVE when

You want to hand edits to Claude Code, Cursor, or any MCP agent.
You need a Changes tab with search, filter, and export.
You want an MIT-licensed tool.

Pick Dialkit when

Dialkit's specific UX or integrations match your stack better.

Feature	DIVE	Dialkit
Visual editing on a scriptable webpage	Yes, typography, colour, layout, spacing, motion and effects on localhost, staging or production pages the extension can script. Browser-protected pages are excluded.	Yes
MCP (Model Context Protocol) handoff to AI agents	Yes, Cloud, Local, and Self-hosted modes; eight common session tools, plus Local feedback rounds	No / Limited
Persistent change history (Changes tab)	Yes, searchable, filterable, exportable	Limited
Open source	Yes (MIT)	Check current licence
Price	Free MIT-licensed extension	Check current pricing
Markdown / JSON export of the diff	Yes	Limited
Best fit for	Designers, developers, QA, PMs, content, indie hackers, agencies, vibe coders	Designers / developers editing in-browser

The honest take

If you don't need AI agent handoff, Dialkit and DIVE are both reasonable choices. If you do, DIVE's three MCP modes are the deciding factor.